The following test failed in the JDK24 CI:

vmTestbase/nsk/jdi/EventRequestManager/threadDeathRequests/thrdeathreq001/TestDescription.java

Here's a snippet from the log file:

#section:driver
----------messages:(9/1566)----------
command: driver nsk.jdi.EventRequestManager.threadDeathRequests.thrdeathreq001 -verbose -arch=linux-aarch64 -waittime=5 -debugee.vmkind=java -transport.address=dynamic -debugee.vmkeys="-XX:MaxRAMPercentage=6.25 -Dtest.boot.jdk=/opt/mach5/mesos/work_dir/jib-master/install/jdk/22/36/bundles/linux-aarch64/jdk-22_linux-aarch64_bin.tar.gz/jdk-22 -Djava.io.tmpdir=/opt/mach5/mesos/work_dir/slaves/a4a7850a-7c35-410a-b879-d77fbb2f6087-S164771/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/832179e9-c454-491c-9611-2006b275cfe4/runs/d3ecb38c-fcbe-4893-af5b-4d29cba9dc18/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdi/tmp -Dcom.oracle.usagetracker.config.file=/opt/mach5/mesos/work_dir/slaves/a4a7850a-7c35-410a-b879-d77fbb2f6087-S164771/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/832179e9-c454-491c-9611-2006b275cfe4/runs/d3ecb38c-fcbe-4893-af5b-4d29cba9dc18/./testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdi/usage-tracker.cfg "
reason: User specified action: run driver nsk.jdi.EventRequestManager.threadDeathRequests.thrdeathreq001 -verbose -arch=${os.family}-${os.simpleArch} -waittime=5 -debugee.vmkind=java -transport.address=dynamic -debugee.vmkeys="${test.vm.opts} ${test.java.opts}"
started: Fri Aug 09 18:37:43 UTC 2024
Mode: agentvm
Agent id: 7
Additional exports to unnamed modules from @modules: java.base/jdk.internal.misc
Additional opens to unnamed modules from @modules: java.base/jdk.internal.misc
finished: Fri Aug 09 18:37:44 UTC 2024
elapsed time (seconds): 1.061
----------configuration:(17/2167)----------

<snip>

----------System.out:(55/7057)*----------
[18:37:43.629] binder> VirtualMachineManager: version 24.0
[18:37:43.630] binder> Finding connector: default
[18:37:43.630] binder> LaunchingConnector:
[18:37:43.630] binder> name: com.sun.jdi.CommandLineLaunch
[18:37:43.630] binder> description: Launches target using Sun Java VM command line and attaches to it
[18:37:43.630] binder> transport: com.sun.tools.jdi.SunCommandLineLauncher$2@20d865bd
[18:37:43.648] binder> Connector arguments:
[18:37:43.648] binder> main=nsk.jdi.EventRequestManager.threadDeathRequests.thrdeathreq001t \u0000-verbose\u0000 \u0000-arch=linux-aarch64\u0000 \u0000-waittime=5\u0000 \u0000-debugee.vmkind=java\u0000 \u0000-transport.address=dynamic\u0000 \u0000-debugee.vmkeys="-XX:MaxRAMPercentage=6.25 -Dtest.boot.jdk=/opt/mach5/mesos/work_dir/jib-master/install/jdk/22/36/bundles/linux-aarch64/jdk-22_linux-aarch64_bin.tar.gz/jdk-22 -Djava.io.tmpdir=/opt/mach5/mesos/work_dir/slaves/a4a7850a-7c35-410a-b879-d77fbb2f6087-S164771/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/832179e9-c454-491c-9611-2006b275cfe4/runs/d3ecb38c-fcbe-4893-af5b-4d29cba9dc18/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdi/tmp -Dcom.oracle.usagetracker.config.file=/opt/mach5/mesos/work_dir/slaves/a4a7850a-7c35-410a-b879-d77fbb2f6087-S164771/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/832179e9-c454-491c-9611-2006b275cfe4/runs/d3ecb38c-fcbe-4893-af5b-4d29cba9dc18/./testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdi/usage-tracker.cfg "\u0000 \u0000-pipe.port=49851\u0000
[18:37:43.648] binder> includevirtualthreads=y
[18:37:43.648] binder> quote=\u0000
[18:37:43.648] binder> home=/opt/mach5/mesos/work_dir/jib-master/install/jdk-24+11-1092/linux-aarch64-debug.jdk/jdk-24/fastdebug
[18:37:43.648] binder> vmexec=java
[18:37:43.648] binder> suspend=true
[18:37:43.648] binder> options=-XX:MaxRAMPercentage=6.25 -Dtest.boot.jdk=/opt/mach5/mesos/work_dir/jib-master/install/jdk/22/36/bundles/linux-aarch64/jdk-22_linux-aarch64_bin.tar.gz/jdk-22 -Djava.io.tmpdir=/opt/mach5/mesos/work_dir/slaves/a4a7850a-7c35-410a-b879-d77fbb2f6087-S164771/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/832179e9-c454-491c-9611-2006b275cfe4/runs/d3ecb38c-fcbe-4893-af5b-4d29cba9dc18/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdi/tmp -Dcom.oracle.usagetracker.config.file=/opt/mach5/mesos/work_dir/slaves/a4a7850a-7c35-410a-b879-d77fbb2f6087-S164771/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/832179e9-c454-491c-9611-2006b275cfe4/runs/d3ecb38c-fcbe-4893-af5b-4d29cba9dc18/./testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdi/usage-tracker.cfg -classpath \u0000/opt/mach5/mesos/work_dir/slaves/a4a7850a-7c35-410a-b879-d77fbb2f6087-S164771/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/832179e9-c454-491c-9611-2006b275cfe4/runs/d3ecb38c-fcbe-4893-af5b-4d29cba9dc18/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdi/classes/2/vmTestbase/nsk/jdi/EventRequestManager/threadDeathRequests/thrdeathreq001/TestDescription.d:/opt/mach5/mesos/work_dir/slaves/a4a7850a-7c35-410a-b879-d77fbb2f6087-S164771/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/832179e9-c454-491c-9611-2006b275cfe4/runs/d3ecb38c-fcbe-4893-af5b-4d29cba9dc18/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdi/classes/2/vmTestbase:/opt/mach5/mesos/work_dir/slaves/a4a7850a-7c35-410a-b879-d77fbb2f6087-S164771/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/832179e9-c454-491c-9611-2006b275cfe4/runs/d3ecb38c-fcbe-4893-af5b-4d29cba9dc18/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdi/classes/2/test/lib\u0000
[18:37:43.649] binder> Launching debugee
[18:37:43.821] binder> Waiting for VM initialized
[18:37:43.821] Initial VMStartEvent received: VMStartEvent in thread main
[18:37:44.400] Creating ThreadDeathRequest #0 with the property (first,a quick)...
[18:37:44.400] Creating ThreadDeathRequest #1 with the property (second,brown)...
[18:37:44.400] Creating ThreadDeathRequest #2 with the property (third,fox)...
[18:37:44.400] Creating ThreadDeathRequest #3 with the property (fourth,jumps)...
[18:37:44.400] Creating ThreadDeathRequest #4 with the property (fifth,over)...
[18:37:44.400] Creating ThreadDeathRequest #5 with the property (sixth,the lazy)...
[18:37:44.400] Creating ThreadDeathRequest #6 with the property (seventh,dog)...
[18:37:44.418]
1) Getting ThreadDeathRequest objects with disabled event requests...
[18:37:44.418] Found expected ThreadDeathRequest object with the property: (first,a quick)
[18:37:44.419] Found expected ThreadDeathRequest object with the property: (second,brown)
[18:37:44.419] Found expected ThreadDeathRequest object with the property: (third,fox)
[18:37:44.419] Found expected ThreadDeathRequest object with the property: (fourth,jumps)
[18:37:44.419] Found expected ThreadDeathRequest object with the property: (fifth,over)
[18:37:44.419] Found expected ThreadDeathRequest object with the property: (sixth,the lazy)
[18:37:44.419] Found expected ThreadDeathRequest object with the property: (seventh,dog)
[18:37:44.439]
2) Getting ThreadDeathRequest objects with enabled event requests...
[18:37:44.439] Found expected ThreadDeathRequest object with the property: (first,a quick)
[18:37:44.439] Found expected ThreadDeathRequest object with the property: (second,brown)
[18:37:44.439] Found expected ThreadDeathRequest object with the property: (third,fox)
[18:37:44.439] Found expected ThreadDeathRequest object with the property: (fourth,jumps)
[18:37:44.439] Found expected ThreadDeathRequest object with the property: (fifth,over)
[18:37:44.439] Found expected ThreadDeathRequest object with the property: (sixth,the lazy)
[18:37:44.439] Found expected ThreadDeathRequest object with the property: (seventh,dog)
[18:37:44.441] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.443] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.444] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.444] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.446] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.460] # ERROR: FAILURE in EventListener: caught unexpected com.sun.jdi.VMDisconnectedException: connection is closed
The following stacktrace is for failure analysis.
nsk.share.TestFailure: FAILURE in EventListener: caught unexpected com.sun.jdi.VMDisconnectedException: connection is closed
at nsk.share.Log.logExceptionForFailureAnalysis(Log.java:377)
at nsk.share.Log.complain(Log.java:348)
at nsk.jdi.EventRequestManager.threadDeathRequests.thrdeathreq001$EventListener.run(thrdeathreq001.java:227)
[18:37:44.469] EventListener: exiting
[18:37:44.546] Debuggee's process finished with status: 95
----------System.err:(19/1315)----------
com.sun.jdi.VMDisconnectedException: connection is closed
at jdk.jdi/com.sun.tools.jdi.TargetVM.send(TargetVM.java:293)
at jdk.jdi/com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:1172)
at jdk.jdi/com.sun.tools.jdi.PacketStream.send(PacketStream.java:79)
at jdk.jdi/com.sun.tools.jdi.JDWP$ThreadReference$Name.enqueueCommand(JDWP.java:5179)
at jdk.jdi/com.sun.tools.jdi.JDWP$ThreadReference$Name.process(JDWP.java:5165)
at jdk.jdi/com.sun.tools.jdi.ThreadReferenceImpl.name(ThreadReferenceImpl.java:191)
at jdk.jdi/com.sun.tools.jdi.EventSetImpl$ThreadedEventImpl.toString(EventSetImpl.java:223)
at nsk.jdi.EventRequestManager.threadDeathRequests.thrdeathreq001$EventListener.run(thrdeathreq001.java:215)
java.lang.RuntimeException: TEST FAILED with result 2
at nsk.jdi.EventRequestManager.threadDeathRequests.thrdeathreq001.main(thrdeathreq001.java:80)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:588)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:333)
at java.base/java.lang.Thread.run(Thread.java:1575)

JavaTest Message: Test threw exception: java.lang.RuntimeException
JavaTest Message: shutting down test

result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: TEST FAILED with result 2

The key snippet of the above failure is:

[18:37:44.439] Found expected ThreadDeathRequest object with the property: (fifth,over)
[18:37:44.439] Found expected ThreadDeathRequest object with the property: (sixth,the lazy)
[18:37:44.439] Found expected ThreadDeathRequest object with the property: (seventh,dog)
[18:37:44.441] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.443] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.444] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.444] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.446] EventListener: following JDI event occured: ThreadDeathEvent in thread UsageTracker
[18:37:44.460] # ERROR: FAILURE in EventListener: caught unexpected com.sun.jdi.VMDisconnectedException: connection is closed
The following stacktrace is for failure analysis.
nsk.share.TestFailure: FAILURE in EventListener: caught unexpected com.sun.jdi.VMDisconnectedException: connection is closed
at nsk.share.Log.logExceptionForFailureAnalysis(Log.java:377)
at nsk.share.Log.complain(Log.java:348)
at nsk.jdi.EventRequestManager.threadDeathRequests.thrdeathreq001$EventListener.run(thrdeathreq001.java:227)
[18:37:44.469] EventListener: exiting

I think the EventListener is having problems with the
exiting UsageTracker thread.