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

serviceability/attach/RemovingUnixDomainSocketTest.java failed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 15, 16, 17
    • Fix Version/s: 17
    • Component/s: core-svc
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b10
    • CPU:
      x86_64
    • OS:
      linux

      Description

      The following test failed in the JDK16 CI:

      serviceability/attach/RemovingUnixDomainSocketTest.java

      Here's a snippet from the log file:

      ----------System.out:(32/2659)----------
      Command line: ['/opt/mach5/mesos/work_dir/jib-master/install/jdk-16+3-55/linux-x64-debug.jdk/jdk-16/fastdebug/bin/java' '-XX:MaxRAMPercentage=6' '-XX:NativeMemoryTracking=detail' '-cp' '/opt/mach5/mesos/work_dir/slaves/4728e7c1-7e67-490e-be0f-6bbf2a2f33db-S273/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/4d1e47c5-02f5-451b-9881-260887e6d0f3/runs/7eef243f-83c7-4e19-a4c9-431d6cc7da56/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/classes/0/serviceability/attach/RemovingUnixDomainSocketTest.d:/opt/mach5/mesos/work_dir/slaves/4728e7c1-7e67-490e-be0f-6bbf2a2f33db-S273/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/4d1e47c5-02f5-451b-9881-260887e6d0f3/runs/7eef243f-83c7-4e19-a4c9-431d6cc7da56/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/classes/0/test/lib' 'jdk.test.lib.apps.LingeredApp' 'ae912189-e6d0-4324-9e35-5d0ee36d19ab.lck']
      [jcmd]:/opt/mach5/mesos/work_dir/jib-master/install/jdk-16+3-55/linux-x64-debug.jdk/jdk-16/fastdebug/bin/jcmd -J-XX:MaxRAMPercentage=6 -J-XX:NativeMemoryTracking=detail 7890 VM.version
      [2020-06-23T05:38:27.493747386Z] Gathering output for process 7924
      [jcmd] 7890:
      [2020-06-23T05:38:28.885343285Z] Waiting for completion for process 7924
      [2020-06-23T05:38:28.885633392Z] Waiting for completion finished for process 7924
      jcmd stdout: [Java HotSpot(TM) 64-Bit Server VM version 16-ea+3-55
      JDK 16.0.0
      ];
      jcmd stderr: []
      jcmd exitValue = 0
      [2020-06-23T05:38:28.930226202Z] Waiting for completion for process 7924
      [2020-06-23T05:38:28.930377247Z] Waiting for completion finished for process 7924
      Remove /tmp/.java_pid7890
      [jcmd]:/opt/mach5/mesos/work_dir/jib-master/install/jdk-16+3-55/linux-x64-debug.jdk/jdk-16/fastdebug/bin/jcmd -J-XX:MaxRAMPercentage=6 -J-XX:NativeMemoryTracking=detail 7890 VM.version
      [2020-06-23T05:38:28.969936254Z] Gathering output for process 7973
      [jcmd] 7890:
      [jcmd] Java HotSpot(TM) 64-Bit Server VM version 16-ea+3-55
      [jcmd] JDK 16.0.0
      [2020-06-23T05:38:29.844964734Z] Waiting for completion for process 7973
      [2020-06-23T05:38:29.845645978Z] Waiting for completion finished for process 7973
      jcmd stdout: [];
      jcmd stderr: [Native Memory Tracking did not setup properly, using wrong launcher?
      ]
      jcmd exitValue = 0
      [2020-06-23T05:38:29.845854340Z] Waiting for completion for process 7973
      [2020-06-23T05:38:29.845977432Z] Waiting for completion finished for process 7973
      [2020-06-23T05:38:29.850685290Z] Waiting for completion for process 7973
      [2020-06-23T05:38:29.850868204Z] Waiting for completion finished for process 7973
       LingeredApp stdout: [];
       LingeredApp stderr: []
       LingeredApp exitValue = 0
      ----------System.err:(20/1147)----------
      [jcmd] Java HotSpot(TM) 64-Bit Server VM warning: Native Memory Tracking did not setup properly, using wrong launcher?
       stdout: [];
       stderr: [Native Memory Tracking did not setup properly, using wrong launcher?
      ]
       exitValue = 0

      java.lang.RuntimeException: stderr was not empty
      at jdk.test.lib.process.OutputAnalyzer.stderrShouldBeEmptyIgnoreVMWarnings(OutputAnalyzer.java:145)
      at RemovingUnixDomainSocketTest.runJCmd(RemovingUnixDomainSocketTest.java:69)
      at RemovingUnixDomainSocketTest.main(RemovingUnixDomainSocketTest.java:88)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.base/java.lang.reflect.Method.invoke(Method.java:564)
      at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:298)
      at java.base/java.lang.Thread.run(Thread.java:832)

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

      result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: stderr was not empty


      test result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: stderr was not empty


      It's not clear if the failure is due to "Native Memory Tracking
      did not setup properly, using wrong launcher?" or if it is
      due to "RuntimeException: stderr was not empty".

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              amenkov Alex Menkov
              Reporter:
              dcubed Daniel Daugherty
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: