The following test failed in the JDK26 CI:

serviceability/dcmd/compiler/CodeHeapAnalyticsParams.java

Here's a snippet from the log file:

#section:driver
----------messages:(9/342)----------
command: driver CodeHeapAnalyticsParams
reason: User specified action: run driver CodeHeapAnalyticsParams
started: Wed Jun 18 21:41:56 UTC 2025
Mode: agentvm
Agent id: 8
Process id: 1866522
Additional exports to unnamed modules from @modules: java.base/jdk.internal.misc
finished: Wed Jun 18 21:42:08 UTC 2025
elapsed time (seconds): 11.658
----------configuration:(15/2013)----------

<snip>

----------System.out:(20/1363)----------
Running DCMD 'Compiler.CodeHeap_Analytics all 1' through 'PidJcmdExecutor'
Executing command '[/opt/mach5/mesos/work_dir/jib-master/install/jdk-26+3-216/linux-x64-debug.jdk/jdk-26/fastdebug/bin/jcmd, -J-Djdk.attach.allowStreamingOutput=false, 1866522, Compiler.CodeHeap_Analytics all 1]'
[2025-06-18T21:41:57.388739999Z] Gathering output for process 1866591
[2025-06-18T21:41:57.460354655Z] Waiting for completion for process 1866591
[2025-06-18T21:42:08.191800803Z] Waiting for completion finished for process 1866591
Output and diagnostic info for process 1866591 was saved into 'pid-1866591-output.log'
Command returned with exit code 1
---------------- stdout ----------------
1866522:

---------------- stderr ----------------
com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file /proc/1866522/root/tmp/.java_pid1866522: target process 1866522 doesn't respond within 10500ms or HotSpot VM not loaded
at jdk.attach/sun.tools.attach.VirtualMachineImpl.<init>(VirtualMachineImpl.java:115)
at jdk.attach/sun.tools.attach.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:56)
at jdk.attach/com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:201)
at jdk.jcmd/sun.tools.jcmd.JCmd.executeCommandForPid(JCmd.java:113)
at jdk.jcmd/sun.tools.jcmd.JCmd.main(JCmd.java:97)

----------------------------------------

----------System.err:(22/1298)----------
 stdout: [1866522:
];
 stderr: [com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file /proc/1866522/root/tmp/.java_pid1866522: target process 1866522 doesn't respond within 10500ms or HotSpot VM not loaded
at jdk.attach/sun.tools.attach.VirtualMachineImpl.<init>(VirtualMachineImpl.java:115)
at jdk.attach/sun.tools.attach.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:56)
at jdk.attach/com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:201)
at jdk.jcmd/sun.tools.jcmd.JCmd.executeCommandForPid(JCmd.java:113)
at jdk.jcmd/sun.tools.jcmd.JCmd.main(JCmd.java:97)
]
 exitValue = 1

java.lang.RuntimeException: Expected to get exit value of [0], exit value is: [1]
at jdk.test.lib.process.OutputAnalyzer.shouldHaveExitValue(OutputAnalyzer.java:522)
at CodeHeapAnalyticsParams.main(CodeHeapAnalyticsParams.java:41)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1474)

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

result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Expected to get exit value of [0], exit value is: [1]


test result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Expected to get exit value of [0], exit value is: [1]


Normally a Tier1 test failure would start off as a P2, but, in this case,
the change sets associated with this build-ID are all for Graal so it
is likely that this issue won't reproduce in the next build-ID. That
would make this an intermittent Tier1 failure which can start out as P3.