Bug ID: JDK-8336145 Three SA tests Passed but then timed out in same test run on macOS

Versions (Unresolved/Resolved/Fixed)

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

Test:  serviceability/sa/ClhsdbAttachDifferentJVMs.java

Test PASSED
----------System.err:(1/15)----------
STATUS:Passed.

test result: Error. Program `/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-24+6-606/macosx-aarch64-debug.jdk/jdk-24/fastdebug/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 1268665ms).

Test: serviceability/sa/ClhsdbAttach.java

Test PASSED
----------System.err:(1/15)----------
STATUS:Passed.

test result: Error. Program `/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-24+6-606/macosx-aarch64-debug.jdk/jdk-24/fastdebug/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 1198741ms).

Test: serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.java

[2024-07-10T18:56:58.341301Z] Gathering output for process 64649
[2024-07-10T18:56:58.392848Z] Waiting for completion for process 64649
[2024-07-10T19:10:38.867029Z] Waiting for completion finished for process 64649
Success!
----------System.err:(3/35)----------

JavaTest Message: Test complete.

result: Error. Agent error: java.lang.Exception: Agent 21 timed out with a timeout of 480 seconds; check console log for any additional details

Hmm. This is what top showed after the failure: PID COMMAND %CPU TIME 107 mds 141.5 03:52:33 296 mds_stores 127.8 11:04:57 66127 jhsdb 97.4 00:02.42 Nothing else significant after these entries. mds is used by Spotlight to index all the files for search purposes. Looks like it became very active. It is very I/O intensive, so can tend to bring other processes to a crawl even if there is still CPU bandwidth. We should probably have Spotlight off on these machines.

10-07-2024

It's probably JDK-8253074. coresymbolicationd running amok.

10-07-2024

It looks like the tests all got hungup on something, but then eventually completed. You see the timeouts while waiting for the SA command to complete. Probably some sort of OS glitch. Note they all started around the same time. All 3 show something like the following: [2024-07-10T18:57:03.666194Z] Gathering output for process 64682 The time for this log entry is 18:57 for all 3 tests. I'm pretty sure we've seen this before, but it has been a while. I'll see if I can track down the bug.

10-07-2024