JDK-8151492 : [TESTBUG] java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java times out
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang.invoke
  • Affected Version: 9,10,12,13
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2016-03-09
  • Updated: 2020-03-19
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.
Other
tbd_majorUnresolved
Related Reports
Duplicate :  
JDK-8209869 - java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java fail with timeout
Relates :  
JDK-8059070 - [TESTBUG] java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java failed - timeout
Sub Tasks
JDK-8217349 :  
Problem list java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java - Resolved
Description
The test [java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java times out in the hotspot compiler nightlies.

The timeout occurs on a Windows machine  (Intel Xeon 3017 MHz, 2 cores, 11G, Win32 / Windows 8.1 Enterprise). The test was run with the following command-line arguments:

-server -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateCoredumpOnCrash -ea -esa -XX:-TieredCompilation -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:+IgnoreUnrecognizedVMOptions -XX:-DoEscapeAnalysis -XX:+AggressiveOpts 

result: Error. Program `C:\local\aurora\CommonData\JDK_DIR\bin\java' timed out (timeout set to 1920000ms, elapsed time was 1922292ms).
Comments
[~mikael] probably best to problem list it in 12. TimeLimitedRunner does not work as intended and so I assign this to [~kshefov] who is the author of this test.
17-01-2019
I was just about to problem list this test, but if a fix is on its way I'll hold off.
17-01-2019
[~kshefov] you have fixed the timeout issues a couple of times (JDK-8062904 and JDK-8059070). I suspect TimeLimitedRunner was intended to help but I don't think it's a good idea. The logs show that the test was interrupted before the TimeLimitedRunner completes one execution of the target call. In some cases, it shows the test actually completed. I also wonder if the default number of iterations should be adjusted? -DtestLimit=2000 Number of iterations according to -DtestLimit is 117 (1989 cases) Number of iterations is set to 117 (1989 cases) Each iteration runs 17 cases. We may workaround this by setting -DtestLimit so that it can run a few iterations. diff --git a/test/jdk/java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java b/test/jdk/java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java --- a/test/jdk/java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java +++ b/test/jdk/java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java @@ -36,7 +36,7 @@ * @build LambdaFormTestCase * @build LFCachingTestCase * @build LFMultiThreadCachingTest - * @run main/othervm LFMultiThreadCachingTest + * @run main/othervm -DtestLimit=100 LFMultiThreadCachingTest */ import test.java.lang.invoke.lib.CodeCacheOverflowProcessor;
16-01-2019
the test also fails in tier1 testing on linux and windows, and in tier4 on solaris w/o any extra flags.
20-09-2018
Another rule RULE "java/lang/invoke/LFCaching/LFMultiThreadCachingTest.java" Timeout none
20-03-2017
Konstantin, you've already worked on a timeout problem related to this test (JDK-8059070). Could you please take a look at this new failure?
09-03-2016