JDK-8260427 : ZGC: misc vmTestbase/gc/gctests timed out
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 16,17
- Priority: P4
- Status: Resolved
- Resolution: Cannot Reproduce
- OS: windows
- CPU: x86_64
- Submitted: 2021-01-26
- Updated: 2021-05-20
- Resolved: 2021-05-03
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.
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 17 |
|---|
17Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
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?
Comments
|