The following test failed in the JDK22 CI:

java/util/concurrent/ConcurrentHashMap/MapLoops.java#id1

Here's a snippet from the log file:

#section:main
----------messages:(6/323)----------
command: main -XX:LockingMode=0 -XX:+VerifyHeavyMonitors MapLoops
reason: User specified action: run main/othervm/timeout=1600 -XX:LockingMode=0 -XX:+VerifyHeavyMonitors MapLoops
started: Wed Nov 29 05:42:51 GMT 2023
Mode: othervm [/othervm specified]
finished: Wed Nov 29 05:43:46 GMT 2023
elapsed time (seconds): 55.643
----------configuration:(0/0)----------
----------System.out:(16/879)----------
Class: java.util.concurrent.ConcurrentHashMap threads: 100 size: 1000 ins: 60 rem: 2 ops: 10000
Threads: 1 : 10253 ns per op 0.102535125s run time
Threads: 1 : 110 ns per op 0.001101583s run time
Threads: 1 : 78 ns per op 7.8525E-4s run time
Threads: 1 : 76 ns per op 7.68875E-4s run time
Threads: 2 : 276 ns per op 0.005536084s run time
Threads: 2 : 1700 ns per op 0.034003791s run time
Threads: 3 : 672 ns per op 0.020186791s run time
Threads: 4 : 44 ns per op 0.001780125s run time
Threads: 6 : 37 ns per op 0.002225708s run time
Threads: 8 : 51 ns per op 0.0041145s run time
Threads: 12 : 31 ns per op 0.003818916s run time
Threads: 16 : 34 ns per op 0.005499916s run time
Threads: 24 : 25 ns per op 0.006157083s run time
Threads: 32 : 34 ns per op 0.011025625s run time
Threads: 48 :
----------System.err:(0/0)----------
----------rerun:(46/7775)*----------

<snip>

result: Failed. Unexpected exit from test [exit code: 134]


Please note the incomplete output line for "Threads: 48". I don't know
if this is the last test or if there are higher thread counts with this test.

We have seen other strange failures on macosx with "exit code: 134"
so I've added the 'macosx-exit-code-134' label here.