-
Bug
-
Resolution: Unresolved
-
P4
-
25
-
x86_64
-
windows_10
Mainly filing for tracking purposes as there is nothing to go on.
Test: sanity/client/SwingSet/src/TabbedPaneDemoTest.java
[2025-03-13T11:38:17,579Z] STDOUT:
[2025-03-13T11:38:17,579Z] Timeout signalled after 240 seconds
[2025-03-13T11:38:17,580Z] STDERR:
[2025-03-13T11:38:17,580Z]
[2025-03-13T11:38:17,580Z] TEST RESULT: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-25+14-1563\windows-x64.jdk\jdk-25\bin\javac' timed out (timeout set to 240000ms, elapsed time including timeout handling was 1152053ms).
but then the whole test process made no further progress for 24 minutes and the test task then timed out:
[2025-03-13T12:02:19,988Z][ERROR][pool-2-thread-1][c.o.j.s.e.SparkyExecutorRunner] Timeout after PT1H while 'Running tests open/test/jdk/:jdk_client_sanity' in phase EXECUTION
[2025-03-13T12:02:20,005Z][INFO][pool-2-thread-1][c.o.j.s.e.SparkyExecutorRunner] Running task phase POST_EXECUTION with timeout set to 90 minutes
Problem occurred on Windows 10. No failure handler artifacts were available - no diagnsostic tools were able to run.
Test: sanity/client/SwingSet/src/TabbedPaneDemoTest.java
[2025-03-13T11:38:17,579Z] STDOUT:
[2025-03-13T11:38:17,579Z] Timeout signalled after 240 seconds
[2025-03-13T11:38:17,580Z] STDERR:
[2025-03-13T11:38:17,580Z]
[2025-03-13T11:38:17,580Z] TEST RESULT: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-25+14-1563\windows-x64.jdk\jdk-25\bin\javac' timed out (timeout set to 240000ms, elapsed time including timeout handling was 1152053ms).
but then the whole test process made no further progress for 24 minutes and the test task then timed out:
[2025-03-13T12:02:19,988Z][ERROR][pool-2-thread-1][c.o.j.s.e.SparkyExecutorRunner] Timeout after PT1H while 'Running tests open/test/jdk/:jdk_client_sanity' in phase EXECUTION
[2025-03-13T12:02:20,005Z][INFO][pool-2-thread-1][c.o.j.s.e.SparkyExecutorRunner] Running task phase POST_EXECUTION with timeout set to 90 minutes
Problem occurred on Windows 10. No failure handler artifacts were available - no diagnsostic tools were able to run.