-
Bug
-
Resolution: Cannot Reproduce
-
P2
-
19, 20
-
x86_64
-
windows
The following test timed out in the JDK19 CI:
gc/z/TestHighUsage.java
Here's a snippet from the log file:
#section:main
----------messages:(6/225)----------
command: main gc.z.TestHighUsage
reason: User specified action: run main/othervm gc.z.TestHighUsage
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 1595.567
----------configuration:(0/0)----------
----------System.out:(8/1709)*----------
Command line: [c:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-19+27-2061\\windows-x64-debug.jdk\\jdk-19\\fastdebug\\bin\\java.exe -cp C:\\sb\\prod\\1654943217\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_hotspot_gc\\classes\\2\\gc\\z\\TestHighUsage.d;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-19+27-2061\\src.full\\open\\test\\hotspot\\jtreg\\gc\\z;C:\\sb\\prod\\1654943217\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_hotspot_gc\\classes\\2\\test\\lib;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-19+27-2061\\src.full\\open\\test\\lib;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\6.1\\1\\bundles\\jtreg-6.1+1.zip\\jtreg\\lib\\javatest.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\6.1\\1\\bundles\\jtreg-6.1+1.zip\\jtreg\\lib\\jtreg.jar -XX:MaxRAMPercentage=4.16667 -Djava.io.tmpdir=c:\\sb\\prod\\1654943217\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_hotspot_gc\\tmp -Xcomp -XX:+CreateCoredumpOnCrash -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -server -XX:+TieredCompilation -XX:+UseZGC -XX:-ZProactive -Xms128M -Xmx128M -XX:ParallelGCThreads=1 -XX:ConcGCThreads=1 -Xlog:gc,gc+start gc.z.TestHighUsage$Test ]
[2022-06-11T11:44:00.891137500Z] Gathering output for process 10808
[2022-06-11T11:54:48.953963700Z] Waiting for completion for process 10808
[2022-06-11T11:54:49.125840Z] Waiting for completion finished for process 10808
Timeout refired 1200 times
Output and diagnostic info for process 10808 was saved into 'pid-10808-output.log'
[2022-06-11T11:55:42.847073400Z] Waiting for completion for process 10808
[2022-06-11T11:55:42.847073400Z] Waiting for completion finished for process 10808
----------System.err:(1/16)----------
STATUS:Passed.
----------rerun:(46/5693)*----------
The test timed out at 1200 seconds, but managed to pass while
the timeout handler was running at 1595.567 seconds. The test
has a default timeout value of 120 seconds/2 minutes and, with
a timeoutFactor of 10, that gets us to a timeout value of 1200.
The execution times should be checked on windows-x64-debug.
If the average is close to 1200, then consider bumping the
default timeout value to 180.
gc/z/TestHighUsage.java
Here's a snippet from the log file:
#section:main
----------messages:(6/225)----------
command: main gc.z.TestHighUsage
reason: User specified action: run main/othervm gc.z.TestHighUsage
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 1595.567
----------configuration:(0/0)----------
----------System.out:(8/1709)*----------
Command line: [c:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-19+27-2061\\windows-x64-debug.jdk\\jdk-19\\fastdebug\\bin\\java.exe -cp C:\\sb\\prod\\1654943217\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_hotspot_gc\\classes\\2\\gc\\z\\TestHighUsage.d;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-19+27-2061\\src.full\\open\\test\\hotspot\\jtreg\\gc\\z;C:\\sb\\prod\\1654943217\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_hotspot_gc\\classes\\2\\test\\lib;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-19+27-2061\\src.full\\open\\test\\lib;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\6.1\\1\\bundles\\jtreg-6.1+1.zip\\jtreg\\lib\\javatest.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\6.1\\1\\bundles\\jtreg-6.1+1.zip\\jtreg\\lib\\jtreg.jar -XX:MaxRAMPercentage=4.16667 -Djava.io.tmpdir=c:\\sb\\prod\\1654943217\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_hotspot_gc\\tmp -Xcomp -XX:+CreateCoredumpOnCrash -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -server -XX:+TieredCompilation -XX:+UseZGC -XX:-ZProactive -Xms128M -Xmx128M -XX:ParallelGCThreads=1 -XX:ConcGCThreads=1 -Xlog:gc,gc+start gc.z.TestHighUsage$Test ]
[2022-06-11T11:44:00.891137500Z] Gathering output for process 10808
[2022-06-11T11:54:48.953963700Z] Waiting for completion for process 10808
[2022-06-11T11:54:49.125840Z] Waiting for completion finished for process 10808
Timeout refired 1200 times
Output and diagnostic info for process 10808 was saved into 'pid-10808-output.log'
[2022-06-11T11:55:42.847073400Z] Waiting for completion for process 10808
[2022-06-11T11:55:42.847073400Z] Waiting for completion finished for process 10808
----------System.err:(1/16)----------
STATUS:Passed.
----------rerun:(46/5693)*----------
The test timed out at 1200 seconds, but managed to pass while
the timeout handler was running at 1595.567 seconds. The test
has a default timeout value of 120 seconds/2 minutes and, with
a timeoutFactor of 10, that gets us to a timeout value of 1200.
The execution times should be checked on windows-x64-debug.
If the average is close to 1200, then consider bumping the
default timeout value to 180.
- is cloned by
-
JDK-8308843 Generational ZGC: Remove gc/z/TestHighUsage.java
- Resolved