JDK-8035328 : closed/compiler/6595044/Main.java failed with timeout
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.
Nighty test closed/compiler/6595044/Main.java failed with timeout in RT nightly test run.
Here is the evaluation:
This bug is not a test bug. The test executes hundreds of small methods consisting of only a return statement multiple times. This was intended to test for an old (closed) bug in the C2 compiler. The timeout arises when the tiered compilation policy decides to recompile the caller method and therefore marks it as non-entrant. The method is still in use but call sites are not patched. See line 1179 of sharedRuntime.cpp:
// We do not patch the call site if the caller nmethod has been made non-entrant.
As a result, all call sites have to be resolved on every call which is costly and leads to the timeout (4mins vs. 17s). The solution is to patch not entrant call sites as well.
My non-confidential comment doesn't have anything in that requires screening.
When I added my failure sighting, I did the split the data into two comments thing;
one is public and one requires screening.
This failure mode was spotted in the 2014-04-30 RT_Baseline nightly:
This test failed due to a timeout. This failure mode is an instance
of the following unresolved bug:
JDK-8035328 [TESTBUG] Test closed/compiler/6595044/Main.java failed with timeout.
This failure instance appears to be failing DKFL matching due to
the missing VM version info in this run.