-
Bug
-
Resolution: Unresolved
-
P4
-
23
-
aarch64
-
os_x
The following test timed out in the JDK23 CI:
serviceability/tmtools/jstack/SpreadLockTest.java
Here's a snippet from the log file:
#section:main
----------messages:(9/433)----------
command: main -XX:+UsePerfData SpreadLockTest
reason: User specified action: run main/othervm -XX:+UsePerfData SpreadLockTest
started: Tue Jan 09 16:20:21 GMT 2024
Mode: othervm [/othervm specified]
Additional options from @modules: --add-modules java.base --add-exports java.base/jdk.internal.misc=ALL-UNNAMED
Timeout information:
--- Timeout information end.
finished: Tue Jan 09 16:30:35 GMT 2024
elapsed time (seconds): 614.052
----------configuration:(4/111)----------
Boot Layer
add modules: java.base
add exports: java.base/jdk.internal.misc ALL-UNNAMED
----------System.out:(6/712)----------
[2024-01-09T16:20:21.717203Z] started process 47156 [/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-23+5-261/macosx-aarch64-debug.jdk/jdk-23/fastdebug/bin/jstack, 47154] with out/err redirected to './out.6131805621279845866.txt' and './err.6131805621279845866.txt'
Timeout signalled after 480 seconds
[2024-01-09T16:29:19.015118Z] process 47156 finished with exit code = 134
Process output: Exit code: 134
stdout:stderr:
[2024-01-09T16:29:19.032968Z] started process 47363 [/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-23+5-261/macosx-aarch64-debug.jdk/jdk-23/fastdebug/bin/jstack, 47154] with out/err redirected to './out.18260050878955442506.txt' and './err.18260050878955442506.txt'
----------System.err:(0/0)----------
----------rerun:(36/8944)*----------
<snip>
result: Error. Program `/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-23+5-261/macosx-aarch64-debug.jdk/jdk-23/fastdebug/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 614042ms).
This failure was first spotted in jdk-23+5-261-tier1 which would normally
start out as a P2 bug, but the changeset in this build-ID does not appear
to be related so I've started this a P3. The changesets in the next four
build-IDs also appear to be unrelated.
serviceability/tmtools/jstack/SpreadLockTest.java
Here's a snippet from the log file:
#section:main
----------messages:(9/433)----------
command: main -XX:+UsePerfData SpreadLockTest
reason: User specified action: run main/othervm -XX:+UsePerfData SpreadLockTest
started: Tue Jan 09 16:20:21 GMT 2024
Mode: othervm [/othervm specified]
Additional options from @modules: --add-modules java.base --add-exports java.base/jdk.internal.misc=ALL-UNNAMED
Timeout information:
--- Timeout information end.
finished: Tue Jan 09 16:30:35 GMT 2024
elapsed time (seconds): 614.052
----------configuration:(4/111)----------
Boot Layer
add modules: java.base
add exports: java.base/jdk.internal.misc ALL-UNNAMED
----------System.out:(6/712)----------
[2024-01-09T16:20:21.717203Z] started process 47156 [/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-23+5-261/macosx-aarch64-debug.jdk/jdk-23/fastdebug/bin/jstack, 47154] with out/err redirected to './out.6131805621279845866.txt' and './err.6131805621279845866.txt'
Timeout signalled after 480 seconds
[2024-01-09T16:29:19.015118Z] process 47156 finished with exit code = 134
Process output: Exit code: 134
stdout:stderr:
[2024-01-09T16:29:19.032968Z] started process 47363 [/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-23+5-261/macosx-aarch64-debug.jdk/jdk-23/fastdebug/bin/jstack, 47154] with out/err redirected to './out.18260050878955442506.txt' and './err.18260050878955442506.txt'
----------System.err:(0/0)----------
----------rerun:(36/8944)*----------
<snip>
result: Error. Program `/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-23+5-261/macosx-aarch64-debug.jdk/jdk-23/fastdebug/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 614042ms).
This failure was first spotted in jdk-23+5-261-tier1 which would normally
start out as a P2 bug, but the changeset in this build-ID does not appear
to be related so I've started this a P3. The changesets in the next four
build-IDs also appear to be unrelated.