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

Multiple SA-JDI tests fail on windows with "Unable to find pid of started process with jps in 30 tries"

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Won't Fix
    • Affects Version/s: 9
    • Fix Version/s: 10
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      svc
    • OS:
      windows_7

      Description

      [2014-10-21T12:30:44.89] # Actual: C:/cygwin/bin/bash C:/local/aurora/sandbox/sca/vmsqe/testbase/vm/9/build/nightly/vm//src/nsk/share/sajdi/run_sajdi.sh nsk.sajdi.ArrayReference.getValues.getvalues001 nsk.sajdi.ArrayReference.getValues.getvalues001a -verbose -arch=windows-i586 -waittime=5 -debugee.vmkind=java "-debugee.vmkeys=-server -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateMinidumpOnCrash -ea -esa -XX:+TieredCompilation -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:+IgnoreUnrecognizedVMOptions -XX:-DoEscapeAnalysis -XX:+AggressiveOpts"
      [2014-10-21T12:30:44.92] core
      [2014-10-21T12:30:45.20] script> Running on windows, adjusting PATH
      [2014-10-21T12:30:45.24] script> # WARNING: Use default connector: attaching_pid
      [2014-10-21T12:30:45.24] script>
      [2014-10-21T12:30:45.24] script> Check if feature not implemented: sun.jvm.hotspot.jdi.SAPIDAttachingConnector
      [2014-10-21T12:30:45.30] script> Feature is implemented: sun.jvm.hotspot.jdi.SAPIDAttachingConnector
      [2014-10-21T12:30:45.30] script>
      [2014-10-21T12:30:45.30] script> Run SA-JDI test:
      [2014-10-21T12:30:45.30] script> DEBUGGER_CLASS: nsk.sajdi.ArrayReference.getValues.getvalues001
      [2014-10-21T12:30:45.30] script> DEBUGGEE_CLASS: nsk.sajdi.ArrayReference.getValues.getvalues001a
      [2014-10-21T12:30:45.30] script> TEST_OPTS: -verbose -arch=windows-i586 -waittime=5 -debugee.vmkind=java -connector=attaching_pid
      [2014-10-21T12:30:45.30] script> CONNECTOR_NAME: sun.jvm.hotspot.jdi.SAPIDAttachingConnector
      [2014-10-21T12:30:45.30] script> DEBUGGER_JAVA: C:/local/aurora/sandbox/sca/vmsqe/jdk/nightly/fastdebug/comp_baseline/windows-i586//bin/java
      [2014-10-21T12:30:45.30] script> JAVA_OPTS: -server -Xmixed -XX:MaxRAMFraction=8 -XX:+CreateMinidumpOnCrash -ea -esa -XX:+TieredCompilation -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:+IgnoreUnrecognizedVMOptions -XX:-DoEscapeAnalysis -XX:+AggressiveOpts -Dsun.jvm.hotspot.runtime.VM.disableVersionCheck=1
      [2014-10-21T12:30:45.30] script> DEBUGGEE_JAVA: C:/local/aurora/sandbox/sca/vmsqe/jdk/nightly/fastdebug/comp_baseline/windows-i586/bin/java
      [2014-10-21T12:30:45.30] script> JAVA_OPTS: -server -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateMinidumpOnCrash -ea -esa -XX:+TieredCompilation -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:+IgnoreUnrecognizedVMOptions -XX:-DoEscapeAnalysis -XX:+AggressiveOpts
      [2014-10-21T12:30:45.33] script>
      [2014-10-21T12:30:45.33] script> Check if generated files exist: debuggee.status DebugServer.status_and_log
      [2014-10-21T12:30:45.33] script>
      [2014-10-21T12:30:45.33] script> Run debuggee: nsk.sajdi.ArrayReference.getValues.getvalues001a
      [2014-10-21T12:30:45.34] C:/local/aurora/sandbox/sca/vmsqe/jdk/nightly/fastdebug/comp_baseline/windows-i586/bin/java -server -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateMinidumpOnCrash -ea -esa -XX:+TieredCompilation -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:+IgnoreUnrecognizedVMOptions -XX:-DoEscapeAnalysis -XX:+AggressiveOpts nsk.sajdi.ArrayReference.getValues.getvalues001a -verbose -arch=windows-i586 -waittime=5 -debugee.vmkind=java -connector=attaching_pid
      [2014-10-21T12:30:47.15] Debuggee class started
      [2014-10-21T12:30:47.23] Debuggee class ready for debugging
      [2014-10-21T12:30:47.70] Will write DEBUGGEE_READY_FOR_DEBUGGING to file debuggee.status
      [2014-10-21T12:30:47.73] Debuggee status written to file
      [2014-10-21T12:30:47.74] File debuggee.status has been created
      [2014-10-21T12:31:58.53] script> # ERROR: Unable to find pid of started process with jps in 30 tries
      [2014-10-21T12:31:58.53] script> Kill process: 11100
      [2014-10-21T12:31:58.57] script> Kill process:
      [2014-10-21T12:31:58.57] # Test level exit status: 97

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                iveresov Igor Veresov
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: