The following two tests timed out in the JDK16 CI:
vmTestbase/gc/gctests/gctest03/gctest03.java
vmTestbase/gc/gctests/gctest02/gctest02.java
Here's a snippet from the gctest03.java log file:
#section:main
----------messages:(6/256)----------
command: main gc.gctests.gctest03.gctest03 10000
reason: User specified action: run main/othervm gc.gctests.gctest03.gctest03 10000
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 539.322
----------configuration:(0/0)----------
----------System.out:(3/197)----------
For random generator using seed: -4705380899977468619
To re-run test with same seed value please add "-Djdk.test.lib.random.seed=-4705380899977468619" to command line.
Timeout refired 480 times
----------System.err:(1/16)----------
STATUS:Passed.
----------rerun:(41/6189)*----------
<snip>
result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-16+34-2213\windows-x64.jdk\jdk-16\bin\java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 539307ms).
Here's a snippet from the gctest02.java log file:
#section:main
----------messages:(6/252)----------
command: main gc.gctests.gctest02.gctest02 100
reason: User specified action: run main/othervm gc.gctests.gctest02.gctest02 100
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 561.028
----------configuration:(0/0)----------
----------System.out:(4/211)----------
For random generator using seed: -4705380899977468619
To re-run test with same seed value please add "-Djdk.test.lib.random.seed=-4705380899977468619" to command line.
Timeout refired 480 times
Test passed.
----------System.err:(1/16)----------
STATUS:Passed.
----------rerun:(41/6187)*----------
<snip>
result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-16+34-2213\windows-x64.jdk\jdk-16\bin\java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 561013ms).
The test task has these JVM args:
-XX:+CreateCoredumpOnCrash -XX:+UseZGC
Based on this line in the log files:
STATUS:Passed.
both tests passed while the timeout handler was running so it looks like these tests
executed just past the default timeout value. Since these failures happened with
ZGC, perhaps the tests need a smaller heap specified?
vmTestbase/gc/gctests/gctest03/gctest03.java
vmTestbase/gc/gctests/gctest02/gctest02.java
Here's a snippet from the gctest03.java log file:
#section:main
----------messages:(6/256)----------
command: main gc.gctests.gctest03.gctest03 10000
reason: User specified action: run main/othervm gc.gctests.gctest03.gctest03 10000
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 539.322
----------configuration:(0/0)----------
----------System.out:(3/197)----------
For random generator using seed: -4705380899977468619
To re-run test with same seed value please add "-Djdk.test.lib.random.seed=-4705380899977468619" to command line.
Timeout refired 480 times
----------System.err:(1/16)----------
STATUS:Passed.
----------rerun:(41/6189)*----------
<snip>
result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-16+34-2213\windows-x64.jdk\jdk-16\bin\java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 539307ms).
Here's a snippet from the gctest02.java log file:
#section:main
----------messages:(6/252)----------
command: main gc.gctests.gctest02.gctest02 100
reason: User specified action: run main/othervm gc.gctests.gctest02.gctest02 100
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 561.028
----------configuration:(0/0)----------
----------System.out:(4/211)----------
For random generator using seed: -4705380899977468619
To re-run test with same seed value please add "-Djdk.test.lib.random.seed=-4705380899977468619" to command line.
Timeout refired 480 times
Test passed.
----------System.err:(1/16)----------
STATUS:Passed.
----------rerun:(41/6187)*----------
<snip>
result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-16+34-2213\windows-x64.jdk\jdk-16\bin\java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 561013ms).
The test task has these JVM args:
-XX:+CreateCoredumpOnCrash -XX:+UseZGC
Based on this line in the log files:
STATUS:Passed.
both tests passed while the timeout handler was running so it looks like these tests
executed just past the default timeout value. Since these failures happened with
ZGC, perhaps the tests need a smaller heap specified?
- duplicates
-
JDK-8260652 vmTestbase/gc/gctests/MTLinkedListGC/MTLinkedListGC.java timed out
-
- Closed
-
- relates to
-
JDK-8259789 vmTestbase/vm/gc/compact tests time out with ZGC
-
- Closed
-
-
JDK-8260684 vmTestbase/gc/gctests/PhantomReference/phantom002/TestDescription.java timed out
-
- Resolved
-
-
JDK-8267484 misc vmTestbase/gc/gctests timed out on a particular machine
-
- Closed
-