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

JDI BScenarios/singlethrd/tc01x002 failed due to timeout


    • Type: Bug
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 14
    • Fix Version/s: tbd
    • Component/s: core-svc
    • Subcomponent:
    • CPU:
    • OS:


      The following test failed in the JDK14 CI:


      Here's a snippet from the log file:

      command: main PropertyResolvingWrapper nsk.jdi.BScenarios.singlethrd.tc01x002 -verbose -arch=${os.family}-${os.simpleArch} -waittime=5 -debugee.vmkind=java -transport.address=dynamic "-debugee.vmkeys=${test.vm.opts} ${test.java.opts}"
      reason: User specified action: run main/othervm PropertyResolvingWrapper nsk.jdi.BScenarios.singlethrd.tc01x002 -verbose -arch=${os.family}-${os.simpleArch} -waittime=5 -debugee.vmkind=java -transport.address=dynamic "-debugee.vmkeys=${test.vm.opts} ${test.java.opts}"
      Mode: othervm [/othervm specified]
      Timeout information:
      --- Timeout information end.
      elapsed time (seconds): 514.896
      run [nsk.jdi.BScenarios.singlethrd.tc01x002, -verbose, -arch=windows-x64, -waittime=5, -debugee.vmkind=java, -transport.address=dynamic, -debugee.vmkeys=-XX:MaxRAMPercentage=3 -Xshare:off -showversion]
      binder> VirtualMachineManager: version 14.0
      binder> Finding connector: default
      binder> LaunchingConnector:
      binder> name: com.sun.jdi.CommandLineLaunch
      binder> description: Launches target using Sun Java VM command line and attaches to it
      binder> transport: com.sun.tools.jdi.SunCommandLineLauncher$1@5ec6c5c8
      binder> Connector arguments:
      binder> home=c:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-14+26-1241\\windows-x64-debug.jdk\\jdk-14\\fastdebug
      binder> vmexec=java
      binder> options=-XX:MaxRAMPercentage=3 -Xshare:off -showversion
      binder> main=nsk.jdi.BScenarios.singlethrd.tc01x002a "-verbose" "-arch=windows-x64" "-waittime=5" "-debugee.vmkind=java" "-transport.address=dynamic" "-debugee.vmkeys=-XX:MaxRAMPercentage=3 -Xshare:off -showversion" "-pipe.port=27148"
      binder> quote="
      binder> suspend=true
      binder> Launching debugee
      binder> Waiting for VM initialized
      Initial VMStartEvent received: VMStartEvent in thread main
      debugee.stderr> java version "14-ea" 2020-03-17
      debugee.stderr> Java(TM) SE Runtime Environment (fastdebug build 14-ea+26-1241)
      debugee.stderr> Java HotSpot(TM) 64-Bit Server VM (fastdebug build 14-ea+26-1241, mixed mode)
      binder> Received expected signal from debugee: ready

      Tested class :nsk.jdi.BScenarios.singlethrd.tc01x002a
      binder> Breakpoint set:
      breakpoint request nsk.jdi.BScenarios.singlethrd.tc01x002a:69 (disabled)
      debugee.stderr> performTest::line 0
       event ===>>> BreakpointEvent@nsk.jdi.BScenarios.singlethrd.tc01x002a:69 in thread main
      BreakpointEvent arrived. Location - 69 line

      debugee.stderr> performTest::breakpoint line
       event ===>>> StepEvent@nsk.jdi.BScenarios.singlethrd.tc01x002a:70 in thread main
      event info:
      thread - main
      source - tc01x002a.java
      method - performTest
      line - 70

      debugee.stderr> performTest::creating tc01x002aClass1 object
       event ===>>> StepEvent@nsk.jdi.BScenarios.singlethrd.tc01x002a:71 in thread main
      event info:
      thread - main
      source - tc01x002a.java
      method - performTest
      line - 71

       event ===>>> StepEvent@nsk.jdi.BScenarios.singlethrd.tc01x002aClass1:76 in thread main
      event info:
      thread - main
      source - tc01x002a.java
      method - <init>
      line - 76
      StepEvent steps to the expected line 76


      debugee.stderr> tc01x002aClass1::constructor is called
      debugee.stderr> quit
      debugee.stderr> completed succesfully.
      Timeout refired 480 times
      java version "14-ea" 2020-03-17
      Java(TM) SE Runtime Environment (fastdebug build 14-ea+26-1241)
      Java HotSpot(TM) 64-Bit Server VM (fastdebug build 14-ea+26-1241, mixed mode)

      So the test timed out at 480 seconds/8 minutes. While JTREG
      was doing the timeout handler, it appears that the test passed.
      See the "TEST FINISHES" at the end of the log file.

      > elapsed time (seconds): 514.896

      shows that perhaps the test needs a little longer to run.
      Perhaps changing the default timeout value from
      120 seconds/2 minutes to 180 seconds/3 minutes
      would give the test time to finish on slower hosts.
      With the default timeout factor (4X) that would give
      the test 720 seconds/12 minutes instead of
      480 seconds/8 minutes.

      I filed a very similar bug for a JDI test in another area:

          JDK-8234594 JDI BScenarios/hotswap/tc05x002 failed due to timeout


          Issue Links



              • Assignee:
                dcubed Daniel Daugherty
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: