Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8274026

SA tests are failing on Mac_OS_X_11.6

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: External
    • Affects Version/s: 18
    • Fix Version/s: 18
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • CPU:
      x86_64
    • OS:
      os_x

      Description

      The following tests failed in the JDK18 CI:

      serviceability/sa/TestUniverse.java
      serviceability/sa/TestType.java
      serviceability/sa/TestSysProps.java
      serviceability/sa/TestPrintMdo.java
      serviceability/sa/TestObjectMonitorIterate.java
      serviceability/sa/TestJmapCoreMetaspace.java
      serviceability/sa/TestJmapCore.java
      serviceability/sa/TestJhsdbJstackLock.java
      serviceability/sa/TestJhsdbJstackLineNumbers.java
      serviceability/sa/TestIntConstant.java
      serviceability/sa/TestInstanceKlassSizeForInterface.java
      serviceability/sa/TestInstanceKlassSize.java
      serviceability/sa/TestHeapDumpForInvokeDynamic.java
      serviceability/sa/TestG1HeapRegion.java
      serviceability/sa/TestDefaultMethods.java
      serviceability/sa/TestCpoolForInvokeDynamic.java
      serviceability/sa/TestClhsdbJstackLock.java
      serviceability/sa/TestClassDump.java
      serviceability/sa/JhsdbThreadInfoTest.java
      serviceability/sa/DeadlockDetectionTest.java
      serviceability/sa/ClhsdbWhere.java
      serviceability/sa/ClhsdbVmStructsDump.java
      serviceability/sa/ClhsdbThread.java
      serviceability/sa/ClhsdbSymbol.java
      serviceability/sa/ClhsdbSource.java
      serviceability/sa/ClhsdbScanOops.java#id1
      serviceability/sa/ClhsdbScanOops.java#id0
      serviceability/sa/ClhsdbPstack.java#id1
      serviceability/sa/ClhsdbPstack.java#id0
      serviceability/sa/ClhsdbPrintStatics.java
      serviceability/sa/ClhsdbPrintAs.java
      serviceability/sa/ClhsdbPrintAll.java
      serviceability/sa/ClhsdbPmap.java#id1
      serviceability/sa/ClhsdbPmap.java#id0
      serviceability/sa/ClhsdbLongConstant.java
      serviceability/sa/ClhsdbJstackXcompStress.java
      serviceability/sa/ClhsdbJstack.java#id1
      serviceability/sa/ClhsdbJstack.java#id0
      serviceability/sa/ClhsdbJhisto.java
      serviceability/sa/ClhsdbJdis.java
      serviceability/sa/ClhsdbInspect.java
      serviceability/sa/ClhsdbHistory.java
      serviceability/sa/ClhsdbFlags.java
      serviceability/sa/ClhsdbFindPC.java#id3
      serviceability/sa/ClhsdbFindPC.java#id2
      serviceability/sa/ClhsdbFindPC.java#id1
      serviceability/sa/ClhsdbFindPC.java#id0
      serviceability/sa/ClhsdbField.java
      serviceability/sa/ClhsdbDumpheap.java
      serviceability/sa/ClhsdbDumpclass.java
      serviceability/sa/ClhsdbClasses.java
      serviceability/sa/ClhsdbCDSJstackPrintAll.java
      serviceability/sa/ClhsdbCDSCore.java
      serviceability/sa/ClhsdbAttach.java
      serviceability/sa/CDSJMapClstats.java
      serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.java

      The TestUniverse.java log file shows this:

      ----------System.out:(44/4061)----------
      Starting TestUniverse
      Command line: ['/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-18+16-867/macosx-x64-open.jdk/jdk-18.jdk/Contents/Home/bin/java' '-XX:MaxRAMPercentage=4.16667' '-Djava.io.tmpdir=/System/Volumes/Data/mesos/work_dir/slaves/a2dc162d-743b-4800-9e92-31f85abb45b1-S4173/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/6ec60c4d-87fc-4913-bd59-9b87e3e12993/runs/f0c31ab4-20b5-46c9-b59d-0ecaed642fa7/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/tmp' '-XX:+UnlockExperimentalVMOptions' '-XX:+UseG1GC' '-cp' '/System/Volumes/Data/mesos/work_dir/slaves/a2dc162d-743b-4800-9e92-31f85abb45b1-S4173/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/6ec60c4d-87fc-4913-bd59-9b87e3e12993/runs/f0c31ab4-20b5-46c9-b59d-0ecaed642fa7/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/classes/5/serviceability/sa/TestUniverse.d:/System/Volumes/Data/mesos/work_dir/slaves/a2dc162d-743b-4800-9e92-31f85abb45b1-S4173/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/6ec60c4d-87fc-4913-bd59-9b87e3e12993/runs/f0c31ab4-20b5-46c9-b59d-0ecaed642fa7/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/classes/5/test/lib' 'jdk.test.lib.apps.LingeredApp' 'abe57653-f1d7-4f79-9355-5634f388b798.lck']
      Started LingeredApp with G1GC and pid 90058
      Starting clhsdb against 90058
      Adding 'sudo -E -n' to the command.
      [2021-09-20T19:32:13.598894Z] Gathering output for process 90115
      [2021-09-20T19:32:13.738534Z] Waiting for completion for process 90115
      [2021-09-20T19:32:13.738649Z] Waiting for completion finished for process 90115
      Output:
      Attaching to process 90058, please wait...
      hsdb> hsdb> + verbose true
      hsdb> + universe
      Command not valid until attached to a VM
      hsdb> + quit
      ERROR: attach: task_for_pid(90058) failed: '(os/kern) failure' (5)
      Unable to connect to process ID 90058:

      Can't attach to the process. Could be caused by an incorrect pid or lack of
      privileges.
      sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the process. Could be caused by an incorrect pid or lack of privileges.
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal$BsdDebuggerLocalWorkerThread.execute(BsdDebuggerLocal.java:168)
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.attach(BsdDebuggerLocal.java:282)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.attachDebugger(HotSpotAgent.java:648)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.setupDebuggerDarwin(HotSpotAgent.java:636)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.setupDebugger(HotSpotAgent.java:371)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.go(HotSpotAgent.java:336)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.attach(HotSpotAgent.java:141)
      at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.attachDebugger(CLHSDB.java:188)
      at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:67)
      at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:44)
      at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runCLHSDB(SALauncher.java:281)
      at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:500)
      Caused by: sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the process. Could be caused by an incorrect pid or lack of privileges.
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.attach0(Native Method)
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal$1AttachTask.doit(BsdDebuggerLocal.java:273)
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal$BsdDebuggerLocalWorkerThread.run(BsdDebuggerLocal.java:143)

      [2021-09-20T19:32:13.739839Z] Waiting for completion for process 90115
      [2021-09-20T19:32:13.739900Z] Waiting for completion finished for process 90115
       LingeredApp stdout: [];
       LingeredApp stderr: []
       LingeredApp exitValue = 0
      '^sun.jvm.hotspot.debugger.DebuggerException:.*$' found in stderr: 'sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the process. Could be caused by an incorrect pid or lack of privileges.'

      ----------System.err:(61/4585)----------
      Timed out waiting for the codesign process to complete. Assuming not signed.
       stdout: [Attaching to process 90058, please wait...
      hsdb> hsdb> + verbose true
      hsdb> + universe
      Command not valid until attached to a VM
      hsdb> + quit
      ];
       stderr: [ERROR: attach: task_for_pid(90058) failed: '(os/kern) failure' (5)
      Unable to connect to process ID 90058:

      Can't attach to the process. Could be caused by an incorrect pid or lack of
      privileges.
      sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the process. Could be caused by an incorrect pid or lack of privileges.
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal$BsdDebuggerLocalWorkerThread.execute(BsdDebuggerLocal.java:168)
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.attach(BsdDebuggerLocal.java:282)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.attachDebugger(HotSpotAgent.java:648)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.setupDebuggerDarwin(HotSpotAgent.java:636)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.setupDebugger(HotSpotAgent.java:371)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.go(HotSpotAgent.java:336)
      at jdk.hotspot.agent/sun.jvm.hotspot.HotSpotAgent.attach(HotSpotAgent.java:141)
      at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.attachDebugger(CLHSDB.java:188)
      at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:67)
      at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:44)
      at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runCLHSDB(SALauncher.java:281)
      at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:500)
      Caused by: sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the process. Could be caused by an incorrect pid or lack of privileges.
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal.attach0(Native Method)
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal$1AttachTask.doit(BsdDebuggerLocal.java:273)
      at jdk.hotspot.agent/sun.jvm.hotspot.debugger.bsd.BsdDebuggerLocal$BsdDebuggerLocalWorkerThread.run(BsdDebuggerLocal.java:143)
      ]
       exitValue = 0

      java.lang.RuntimeException: '^sun.jvm.hotspot.debugger.DebuggerException:.*$' found in stderr: 'sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the process. Could be caused by an incorrect pid or lack of privileges.'

      at jdk.test.lib.process.OutputAnalyzer.shouldNotMatch(OutputAnalyzer.java:404)
      at ClhsdbLauncher.runCmd(ClhsdbLauncher.java:151)
      at ClhsdbLauncher.run(ClhsdbLauncher.java:203)
      at TestUniverse.testClhsdbForUniverse(TestUniverse.java:90)
      at TestUniverse.test(TestUniverse.java:98)
      at TestUniverse.main(TestUniverse.java:127)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.base/java.lang.reflect.Method.invoke(Method.java:568)
      at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
      at java.base/java.lang.Thread.run(Thread.java:833)
      java.lang.Error: Test failed with java.lang.RuntimeException: '^sun.jvm.hotspot.debugger.DebuggerException:.*$' found in stderr: 'sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the process. Could be caused by an incorrect pid or lack of privileges.'

      at TestUniverse.main(TestUniverse.java:135)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.base/java.lang.reflect.Method.invoke(Method.java:568)
      at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
      at java.base/java.lang.Thread.run(Thread.java:833)

      JavaTest Message: Test threw exception: java.lang.Error: Test failed with java.lang.RuntimeException: '^sun.jvm.hotspot.debugger.DebuggerException:.*$' found in stderr: 'sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the process. Could be caused by an incorrect pid or lack of privileges.'

      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.Error: Test failed with java.lang.RuntimeException: '^sun.jvm.hotspot.debugger.DebuggerException:.*$' found in stderr: 'sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the process. Could be caused by an incorrect pid or lack of privileges.'
      ----------rerun:(35/7211)*----------


      These failures happened on a test machine running Mac_OS_X_11.6.

      It's not clear whether these failures are related to some change
      in Mac_OS_X_11.6 or whether codesign has something to do
      with this:

      ----------System.err:(61/4585)----------
      Timed out waiting for the codesign process to complete. Assuming not signed.
       stdout: [Attaching to process 90058, please wait...

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              cjplummer Chris Plummer
              Reporter:
              dcubed Daniel Daugherty
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: