The following test timed out in the JDK24 CI:

vmTestbase/gc/gctests/ObjectMonitorCleanup/ObjectMonitorCleanup.java

Here's a snippet from the log file:

#section:main
----------messages:(8/411)----------
command: main -XX:-UseGCOverheadLimit gc.gctests.ObjectMonitorCleanup.ObjectMonitorCleanup
reason: User specified action: run main/othervm -XX:-UseGCOverheadLimit gc.gctests.ObjectMonitorCleanup.ObjectMonitorCleanup
started: Mon Oct 07 04:57:37 GMT 2024
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
finished: Mon Oct 07 05:08:03 GMT 2024
elapsed time (seconds): 625.468
----------configuration:(0/0)----------
----------System.out:(12/277)----------
Stress time: 30 seconds
Stress iterations factor: 1
Stress threads factor: 1
Stress runs factor: 1
Max memory: 1432354816
Sleep time: 500
Iterations: 0
Number of threads: 24
Run GC thread: false
Run mem diag thread: false
Run forever: false
Timeout signalled after 480 seconds
----------System.err:(0/0)----------
----------rerun:(35/8980)*----------

<snip>

result: Error. Program `/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-24+19-2144/macosx-x64.jdk/jdk-24.jdk/Contents/Home/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 625460ms).

Since this is a GC test, I'm starting this one in hotspot/gc for initial triage.