JDK-8208205 : ProblemList tests that fail due to 'Error attaching to process: Can't create thread_db agent!'
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 11,12
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris
  • CPU: x86_64,sparc_64
  • Submitted: 2018-07-25
  • Updated: 2018-08-09
  • Resolved: 2018-07-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.
JDK 11 JDK 12
11 b25Fixed 12Fixed
Description
There are a large number of tests that hit the

    Error attaching to process: Can't create thread_db agent!

error on Solaris SPARCv9 and Solaris-X64. These failures
create quite a bit of noise in the JDK11 and JDK12 CI system.
Comments
$ hg diff test/hotspot/jtreg/ProblemList.txt diff -r 628718bf8970 test/hotspot/jtreg/ProblemList.txt --- a/test/hotspot/jtreg/ProblemList.txt Wed Jul 25 12:32:06 2018 -0400 +++ b/test/hotspot/jtreg/ProblemList.txt Wed Jul 25 14:47:58 2018 -0400 @@ -74,14 +74,43 @@ # :hotspot_runtime runtime/CompressedOops/UseCompressedOops.java 8079353 generic-all +runtime/SharedArchiveFile/SASymbolTableTest.java 8193639 solaris ############################################################################# # :hotspot_serviceability -serviceability/sa/ClhsdbCDSCore.java 8207832 linux-x64 -serviceability/sa/TestRevPtrsForInvokeDynamic.java 8191270 generic-all -serviceability/sa/sadebugd/SADebugDTest.java 8163805 generic-all +serviceability/sa/ClhsdbAttach.java 8193639 solaris +serviceability/sa/ClhsdbCDSCore.java 8207832 linux-x64 +serviceability/sa/ClhsdbField.java 8193639 solaris +serviceability/sa/ClhsdbFindPC.java 8193639 solaris +serviceability/sa/ClhsdbInspect.java 8193639 solaris +serviceability/sa/ClhsdbJdis.java 8193639 solaris +serviceability/sa/ClhsdbJhisto.java 8193639 solaris +serviceability/sa/ClhsdbJstack.java 8193639 solaris +serviceability/sa/ClhsdbLongConstant.java 8193639 solaris +serviceability/sa/ClhsdbPmap.java 8193639 solaris +serviceability/sa/ClhsdbPrintAll.java 8193639 solaris +serviceability/sa/ClhsdbPrintAs.java 8193639 solaris +serviceability/sa/ClhsdbPrintStatics.java 8193639 solaris +serviceability/sa/ClhsdbPstack.java 8193639 solaris +serviceability/sa/ClhsdbRegionDetailsScanOopsForG1.java 8193639 solaris +serviceability/sa/ClhsdbScanOops.java 8193639 solaris +serviceability/sa/ClhsdbSource.java 8193639 solaris +serviceability/sa/ClhsdbSymbol.java 8193639 solaris +serviceability/sa/ClhsdbSymbolTable.java 8193639 solaris +serviceability/sa/ClhsdbThread.java 8193639 solaris +serviceability/sa/ClhsdbWhere.java 8193639 solaris +serviceability/sa/DeadlockDetectionTest.java 8193639 solaris +serviceability/sa/JhsdbThreadInfoTest.java 8193639 solaris +serviceability/sa/sadebugd/SADebugDTest.java 8163805 generic-all +serviceability/sa/TestClassDump.java 8193639 solaris +serviceability/sa/TestCpoolForInvokeDynamic.java 8193639 solaris +serviceability/sa/TestDefaultMethods.java 8193639 solaris +serviceability/sa/TestG1HeapRegion.java 8193639 solaris +serviceability/sa/TestRevPtrsForInvokeDynamic.java 8191270 generic-all +serviceability/sa/TestType.java 8193639 solaris +serviceability/sa/TestUniverse.java 8193639 solaris #############################################################################
25-07-2018
First, the test that originally failed back in JDK10: sun/tools/jhsdb/BasicLauncherTest.java is not being added to the ProblemList because I can't find a recent sighting of that test failing in the named entries in JDK-8193639 or in the test in my lab. I created the original list of additions from my testing on Solaris-X64 for jdk-11+19 and jdk-11+23. Next I added any new test names that are specifically called out comments in JDK-8193639 after verifying that the referenced Mach5 link shows the right failure. Note: If there was just a Mach5 link, but no list of tests, then I didn't chase down those failures. There are limits to even my insanity. :-)
25-07-2018