JDK-8173143 : test/tools/jdeprscan/tests/jdk/jdeprscan/TestRelease.java crash in PhaseChaitin::gather_lrg_masks()
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2017-01-20
  • Updated: 2020-09-01
  • Resolved: 2017-01-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Resolved
Related Reports
Duplicate :  
JDK-8172850 - Anti-dependency on membar causes crash in register allocator due to invalid instruction scheduling
Description
So far we have seen tier1 failures in every single Mach 5 run in jdk9/hs. One test, TestRelease.java, has failed in every single Mach 5 run. In some cases this is the only failure. It fails on different platforms different runs.

The Mach 5 builds I have looked at are the ones labeled as "Fail", I have not looked at the "Incomplete" ones. These are build # 31, 40, 41, 42, 43, 44, 45, 46, 47, 48, 50, 52, 55, 57.

I have sampled five of these and they all contain the same error message:
test result: Error. Agent communication error: java.io.EOFException; check console log for any additional details

Looking at the stdout that is stored in the archive I find:

bash> ACTION: testng -- Error. Agent communication error: java.io.EOFException; check console log for any additional details
bash> REASON: User specified action: run testng jdk.jdeprscan.TestRelease
bash> TIME:   5.765 seconds
bash> messages:
bash> command: testng jdk.jdeprscan.TestRelease
bash> reason: User specified action: run testng jdk.jdeprscan.TestRelease
bash> Mode: agentvm
bash> Additional exports to unnamed modules from @modules: jdk.jdeps/com.sun.tools.jdeprscan
bash> elapsed time (seconds): 5.765

I don't disagree that the reason for the failure is that we ran the test, but I was hoping for a little more detail there.

Also worth noting that even though the test sometimes fails on windows and solaris, there are no files collected from these platforms in the archive.


This test is currently causing a lot of noise up to the point where people risk start ignoring the failure mails. There is also the issue that we are not supposed to integrate jdk9/hs to jdk9/dev unless we have a green Mach 5 build.
Comments
This is a duplicate of JDK-8172850. I was able to reproduce the problem on one of the mach5 machines and verified that my fix solves the issue.
23-01-2017
It's very likely that this is a duplicate of JDK-8172850. Unfortunately, Mach5 is down and therefore I cannot access the logs. I'll check as soon as the system is up again.
23-01-2017
All of the "Agent Communication" errors are caused by bugs in the jtreg version being used in jdk9-hs. jdk9-dev has been upgraded to use jtreg 4.2 b05 which has fixes for these problems. Perhaps jdk9-hs should be upgraded before the sync-down from jdk9-dev? See: JDK-8172709 and CODETOOLS-7901870.
20-01-2017