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

Kitchensink24HStress.java failed with "exit code 139"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 17
    • Fix Version/s: tbd
    • Component/s: hotspot
    • Subcomponent:
    • CPU:
      x86_64
    • OS:
      linux

      Description

      The following test failed in the JDK17 CI:

      applications/kitchensink/Kitchensink24HStress.java

      Here's a snippet from the log file:

      Unexpected exception Connection reset during communication. Check process module status.
       stdout: [];
       stderr: [jfr summary: file is empty '/opt/mach5/mesos/work_dir/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S79890/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/b7d535bd-23c1-42d5-8415-30abec94e422/runs/34050d7a-11b3-47a3-ab37-5bbff1223bb7/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_applications_kitchensink_Kitchensink24HStress_java/scratch/0/jfr-files/external/ks_external13651669406162665848.jfr'
      ]
       exitValue = 1

      Failed to parse file /opt/mach5/mesos/work_dir/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S79890/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/b7d535bd-23c1-42d5-8415-30abec94e422/runs/34050d7a-11b3-47a3-ab37-5bbff1223bb7/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_applications_kitchensink_Kitchensink24HStress_java/scratch/0/perfmon-files/Perfmon.1618159634807.out
      Cannot parse null string
      [Sun Apr 11 16:48:08 UTC 2021] (1618159688818) Picker module is about to shutdown
      Picker module expected time before shutdown for: Jcmd: 30s
      Picker module expected time before shutdown for: Jfr: 3m 20s
      Picker module expected time before shutdown for: Jstat: 5m
      Picker module expected time before shutdown for: Monitor: 1m
      Picker module expected time before shutdown for: NMT: 1m
      Picker module expected time before shutdown for: Perfmon: 5m
      Picker module finished at [Sun Apr 11 16:48:08 UTC 2021]: Monitor
      Picker module finished at [Sun Apr 11 16:48:08 UTC 2021]: Jstat
      Picker module finished at [Sun Apr 11 16:48:08 UTC 2021]: Jfr
      Picker module finished at [Sun Apr 11 16:48:08 UTC 2021]: Jcmd
      Picker module finished at [Sun Apr 11 16:48:08 UTC 2021]: Perfmon
      Waiting until all picker modules finish.
      Picker module finished at [Sun Apr 11 16:48:09 UTC 2021]: NMT
      [Sun Apr 11 16:48:38 UTC 2021] (1618159718862) Picker module has been shutdown
      [Sun Apr 11 16:48:38 UTC 2021] (1618159718863) Stress process is about to shutdown
      Going to request to stop or kill stress process: 12085
      WARNING: The process 12085 has already finished.
      [Sun Apr 11 16:48:38 UTC 2021] (1618159718870) Stress process has been shutdown
      [Sun Apr 11 16:48:38 UTC 2021] Execution finished.
      ----------rerun:(39/9009)*----------

      <snip>

      result: Failed. Unexpected exit from test [exit code: 139]

      Looking through the failure's artifacts I this in JfrPickerModule.err:

      java.io.IOException: Connection reset by peer
              at jdk.attach/sun.tools.attach.VirtualMachineImpl.read(Native Method)
              at jdk.attach/sun.tools.attach.VirtualMachineImpl$SocketInputStream.read(VirtualMachineImpl.java:263)
              at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.readInt(HotSpotVirtualMachine.java:328)
              at jdk.attach/sun.tools.attach.VirtualMachineImpl.execute(VirtualMachineImpl.java:195)
              at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.executeCommand(HotSpotVirtualMachine.java:309)
              at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.executeJCmd(HotSpotVirtualMachine.java:291)
              at jdk.jcmd/sun.tools.jcmd.JCmd.executeCommandForPid(JCmd.java:124)
              at jdk.jcmd/sun.tools.jcmd.JCmd.main(JCmd.java:97)

      and pid-14790-output.log from the same timestamp shows:

      --- ProcessLog ---
      cmd: /opt/mach5/mesos/work_dir/jib-master/install/jdk-17+18-1410/linux-x64-debug.jdk/jdk-17/fastdebug/bin/jfr summary /opt/mach5/mesos/work_dir/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S79890/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/b7d535bd-23c1-42d5-8415-30abec94e422/runs/34050d7a-11b3-47a3-ab37-5bbff1223bb7/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_applications_kitchensink_Kitchensink24HStress_java/scratch/0/jfr-files/external/ks_external13651669406162665848.jfr
      exitvalue: 1
      stderr: jfr summary: file is empty '/opt/mach5/mesos/work_dir/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S79890/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/b7d535bd-23c1-42d5-8415-30abec94e422/runs/34050d7a-11b3-47a3-ab37-5bbff1223bb7/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_applications_kitchensink_Kitchensink24HStress_java/scratch/0/jfr-files/external/ks_external13651669406162665848.jfr'

      stdout:


      I'm starting this bug in hotspot/test since I'm not sure whether
      this is a problem with the test execution infrastructure or not.

        Attachments

          Activity

            People

            Assignee:
            lmesnik Leonid Mesnik
            Reporter:
            dcubed Daniel Daugherty
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: