JDK-8282421 : serviceability/sa/ClhsdbDumpclass.java times out
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 19
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: os_x_10.15
  • CPU: x86_64
  • Submitted: 2022-02-26
  • Updated: 2022-03-25
  • Resolved: 2022-03-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdResolved
Related Reports
Duplicate :  
JDK-8253074 - SA tests time out on macOS after sudo due to runaway coresymbolicationd
Relates :  
JDK-8253074 - SA tests time out on macOS after sudo due to runaway coresymbolicationd
Description
The following test times out in the JDK19 CI:

serviceability/sa/ClhsdbDumpclass.java

Here's a snippet from the log file:

#section:driver
----------messages:(8/225)----------
command: driver ClhsdbDumpclass
reason: User specified action: run driver ClhsdbDumpclass 
Mode: agentvm
Agent id: 9
Timeout refired 480 times
Timeout information:
--- Timeout information end.
elapsed time (seconds): 806.373
----------configuration:(16/2205)----------
Boot Layer
  class path: /System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/javatest.jar 
              /System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/jtreg.jar 
              /System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/junit.jar 
              /System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/hamcrest.jar 
              /System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/testng.jar 
              /System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/jcommander.jar 
              /System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/guice.jar 
  patch:      java.base /System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S13855/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/f68e16a1-5669-4c4f-9de5-c41881181b8e/runs/07b4b368-4b84-4c51-8571-6f6e8c229282/testoutput/test-support/jtreg_open_test_hotspot_jtreg_tier1_serviceability/patches/java.base

Test Layer
  class path: /System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S13855/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/f68e16a1-5669-4c4f-9de5-c41881181b8e/runs/07b4b368-4b84-4c51-8571-6f6e8c229282/testoutput/test-support/jtreg_open_test_hotspot_jtreg_tier1_serviceability/classes/2/serviceability/sa/ClhsdbDumpclass.d
              /System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-19+12-692/src.full/open/test/hotspot/jtreg/serviceability/sa
              /System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S13855/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/f68e16a1-5669-4c4f-9de5-c41881181b8e/runs/07b4b368-4b84-4c51-8571-6f6e8c229282/testoutput/test-support/jtreg_open_test_hotspot_jtreg_tier1_serviceability/classes/2/test/lib
              /System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-19+12-692/src.full/open/test/lib

----------rerun:(29/6251)*----------

<snip>

----------System.out:(2/1024)----------
Starting ClhsdbDumpclass test
Command line: ['/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-19+12-692/macosx-x64-debug.jdk/jdk-19/fastdebug/bin/java' '-XX:MaxRAMPercentage=4.16667' '-Djava.io.tmpdir=/System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S13855/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/f68e16a1-5669-4c4f-9de5-c41881181b8e/runs/07b4b368-4b84-4c51-8571-6f6e8c229282/testoutput/test-support/jtreg_open_test_hotspot_jtreg_tier1_serviceability/tmp' '-Xshare:off' '-showversion' '-cp' '/System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S13855/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/f68e16a1-5669-4c4f-9de5-c41881181b8e/runs/07b4b368-4b84-4c51-8571-6f6e8c229282/testoutput/test-support/jtreg_open_test_hotspot_jtreg_tier1_serviceability/classes/2/serviceability/sa/ClhsdbDumpclass.d:/System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S13855/frameworks/1735e8a2-a1db-478c-
result: Error. Agent error: java.lang.Exception: Agent 9 timed out with a timeout of 480 seconds; check console log for any additional details

This timeout seems to be happening when another test fails due to:

JDK-8253074 SA tests time out on macOS after sudo due to runaway coresymbolicationd

in the same test run.
Comments
Like with JDK-8283354, I'm going to close this as a dup of JDK-8253074, even though it's not in the usual list of tests that fail, and does not show the same symptoms in the log. It is a test timeout, and in this case it doesn't even look like the test got started up, let alone tried to do an attach. As I mentioned in JDK-8283354: > The runaway coresymbolicationd process makes doing the attach extremely slow, so it times out. However the runaway coresymbolicationd process is hogging so much CPU that it can make other processes slow down too, even if not doing anything SA related, and the situation is probably worse if other SA tests are trying to run at the same time and are trying to attach. So basically any timeout on a host that is reproducing the usual list of JDK-8283354 failures is likely also due to the runaway coresymbolicationd process.
25-03-2022