-
Bug
-
Resolution: Unresolved
-
P4
-
26
-
x86_64
-
windows
This test timeout out in the JDK26 CI:
compiler/arguments/TestCompilerCounts.java#id0
#section:driver
----------messages:(11/397)----------
command: driver compiler.arguments.TestCompilerCounts debug
reason: User specified action: run driver compiler.arguments.TestCompilerCounts debug
started: Tue Oct 14 09:15:49 UTC 2025
Mode: agentvm
Agent id: 9
Process id: 25336
Timeout signalled after 120 seconds
Timeout information:
--- Timeout information end.
finished: Tue Oct 14 09:23:29 UTC 2025
elapsed time (seconds): 460.401
----------configuration:(15/1546)*----------
<snip>
Command line: [c:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-26+20-2022\\windows-x64-debug.jdk\\jdk-26\\fastdebug\\bin\\java.exe -cp C:\\sb\\prod\\1760433137\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_tier2_compiler\\classes\\3\\compiler\\arguments\\TestCompilerCounts_id0.d;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-26+20-2022\\src.full\\open\\test\\hotspot\\jtreg\\compiler\\arguments;C:\\sb\\prod\\1760433137\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_tier2_compiler\\classes\\3\\compiler\\arguments\\TestCompilerCounts_id0.d\\test\\lib;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\jtreg.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\junit-platform-console-standalone-1.13.3.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\testng-7.3.0.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\jcommander-1.82.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\guice-5.1.0.jar -server -XX:-NeverActAsServerClassMachine -XX:ActiveProcessorCount=12 -XX:TieredStopAtLevel=4 -XX:NonNMethodCodeHeapSize=5242880 -XX:+PrintFlagsFinal -version ]
[2025-10-14T09:17:49.953484500Z] Gathering output for process 9208
[2025-10-14T09:17:49.953484500Z] Waiting for completion for process 9208
[2025-10-14T09:17:50.614807700Z] Waiting for completion finished for process 9208
----------System.err:(3/38)----------
JavaTest Message: Test complete.
result: Error. "driver" action timed out with a timeout of 120 seconds on agent 9
Based on the start time:
start=Tue Oct 14 09\:15\:46 UTC 2025
and the time stamp on the last command:
[2025-10-14T09:17:50.614807700Z] Waiting for completion finished for process 9208
the test really did execute for > 2:04 which is 124 seconds
and that was to the start of the last command execution.
The timeout did not reproduce in the next five Tier2 job sets
so I've added the 'intermittent' label and I'm starting this issue
off as a P4.
compiler/arguments/TestCompilerCounts.java#id0
#section:driver
----------messages:(11/397)----------
command: driver compiler.arguments.TestCompilerCounts debug
reason: User specified action: run driver compiler.arguments.TestCompilerCounts debug
started: Tue Oct 14 09:15:49 UTC 2025
Mode: agentvm
Agent id: 9
Process id: 25336
Timeout signalled after 120 seconds
Timeout information:
--- Timeout information end.
finished: Tue Oct 14 09:23:29 UTC 2025
elapsed time (seconds): 460.401
----------configuration:(15/1546)*----------
<snip>
Command line: [c:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-26+20-2022\\windows-x64-debug.jdk\\jdk-26\\fastdebug\\bin\\java.exe -cp C:\\sb\\prod\\1760433137\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_tier2_compiler\\classes\\3\\compiler\\arguments\\TestCompilerCounts_id0.d;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-26+20-2022\\src.full\\open\\test\\hotspot\\jtreg\\compiler\\arguments;C:\\sb\\prod\\1760433137\\testoutput\\test-support\\jtreg_open_test_hotspot_jtreg_tier2_compiler\\classes\\3\\compiler\\arguments\\TestCompilerCounts_id0.d\\test\\lib;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\jtreg.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\junit-platform-console-standalone-1.13.3.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\testng-7.3.0.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\jcommander-1.82.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jtreg\\8\\2\\bundles\\jtreg-8+2.zip\\jtreg\\lib\\guice-5.1.0.jar -server -XX:-NeverActAsServerClassMachine -XX:ActiveProcessorCount=12 -XX:TieredStopAtLevel=4 -XX:NonNMethodCodeHeapSize=5242880 -XX:+PrintFlagsFinal -version ]
[2025-10-14T09:17:49.953484500Z] Gathering output for process 9208
[2025-10-14T09:17:49.953484500Z] Waiting for completion for process 9208
[2025-10-14T09:17:50.614807700Z] Waiting for completion finished for process 9208
----------System.err:(3/38)----------
JavaTest Message: Test complete.
result: Error. "driver" action timed out with a timeout of 120 seconds on agent 9
Based on the start time:
start=Tue Oct 14 09\:15\:46 UTC 2025
and the time stamp on the last command:
[2025-10-14T09:17:50.614807700Z] Waiting for completion finished for process 9208
the test really did execute for > 2:04 which is 124 seconds
and that was to the start of the last command execution.
The timeout did not reproduce in the next five Tier2 job sets
so I've added the 'intermittent' label and I'm starting this issue
off as a P4.