-
Bug
-
Resolution: Unresolved
-
P4
-
17, 23, 24
-
x86_64, aarch64
-
os_x
The following test timed out in the JDK24 CI:
java/awt/Focus/FocusTransitionTest/FocusTransitionTest.java
Here's a snippet from the log file:
#section:main
----------messages:(9/329)----------
command: main FocusTransitionTest
reason: User specified action: run main FocusTransitionTest
started: Fri Aug 02 23:45:44 GMT 2024
Mode: othervm
Additional options from @modules: --add-modules java.desktop
Timeout information:
--- Timeout information end.
finished: Fri Aug 02 23:52:17 GMT 2024
elapsed time (seconds): 393.148
----------configuration:(3/40)----------
Boot Layer
add modules: java.desktop
----------System.out:(1/36)----------
Timeout signalled after 240 seconds
----------System.err:(0/0)----------
----------rerun:(45/7213)*----------
<snip>
result: Error. Program `/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-24+10-1003/macosx-x64.jdk/jdk-24.jdk/Contents/Home/bin/java' timed out (timeout set to 240000ms, elapsed time including timeout handling was 393140ms).
There's no indicators in the log file for what caused the timeout.
java/awt/Focus/FocusTransitionTest/FocusTransitionTest.java
Here's a snippet from the log file:
#section:main
----------messages:(9/329)----------
command: main FocusTransitionTest
reason: User specified action: run main FocusTransitionTest
started: Fri Aug 02 23:45:44 GMT 2024
Mode: othervm
Additional options from @modules: --add-modules java.desktop
Timeout information:
--- Timeout information end.
finished: Fri Aug 02 23:52:17 GMT 2024
elapsed time (seconds): 393.148
----------configuration:(3/40)----------
Boot Layer
add modules: java.desktop
----------System.out:(1/36)----------
Timeout signalled after 240 seconds
----------System.err:(0/0)----------
----------rerun:(45/7213)*----------
<snip>
result: Error. Program `/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-24+10-1003/macosx-x64.jdk/jdk-24.jdk/Contents/Home/bin/java' timed out (timeout set to 240000ms, elapsed time including timeout handling was 393140ms).
There's no indicators in the log file for what caused the timeout.