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

JDI BScenarios/hotswap/tc05x002 failed due to timeout

    Details

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

      Description

      The following test failed due to timeout in the JDK14 CI:

      vmTestbase/nsk/jdi/BScenarios/hotswap/tc05x002/TestDescription.java

      Here's a snippet from the log file:

      #section:main
      ----------messages:(6/634)----------
      command: main PropertyResolvingWrapper nsk.jdi.BScenarios.hotswap.tc05x002 ./bin -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.hotswap.tc05x002 ./bin -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): 522.426
      ----------configuration:(0/0)----------
      ----------System.out:(63/2334)*----------
      run [nsk.jdi.BScenarios.hotswap.tc05x002, ./bin, -verbose, -arch=windows-x64, -waittime=5, -debugee.vmkind=java, -transport.address=dynamic, -debugee.vmkeys=-XX:MaxRAMPercentage=6 -server]
      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@7ac5493d
      binder> Connector arguments:
      binder> home=c:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-14+24-1108\\windows-x64-debug.jdk\\jdk-14\\fastdebug
      binder> vmexec=java
      binder> options=-XX:MaxRAMPercentage=6 -server
      binder> main=nsk.jdi.BScenarios.hotswap.tc05x002a "./bin" "-verbose" "-arch=windows-x64" "-waittime=5" "-debugee.vmkind=java" "-transport.address=dynamic" "-debugee.vmkeys=-XX:MaxRAMPercentage=6 -server" "-pipe.port=53160"
      binder> quote="
      binder> suspend=true
      binder> Launching debugee
      binder> Waiting for VM initialized
      Initial VMStartEvent received: VMStartEvent in thread main

      TEST BEGINS
      ===========

       event ===>>> ClassPrepareEvent in thread main
      Tested class :nsk.jdi.BScenarios.hotswap.tc05x002a
      binder> Breakpoint set:
      breakpoint request nsk.jdi.BScenarios.hotswap.tc05x002a:58 (disabled)

       event ===>>> BreakpointEvent@nsk.jdi.BScenarios.hotswap.tc05x002a:58 in thread main
      event info: #1
      thread - main
      source - tc05x002a.java
      method - method_A
      line - 58
      !!!BreakpointEvent steps to the expected line 58!!!

      redefining...
      class-file :newclass\\nsk\\jdi\\BScenarios\\hotswap\\tc05x002a.class

       event ===>>> StepEvent@nsk.jdi.BScenarios.hotswap.tc05x002a.<obsolete>()+1 in thread main
      event info: #1
      thread - main
      source - tc05x002a.java
      method - <obsolete>
      line - -1
      <obsolete> method is skipped
      !!!Expected step event!!!


       event ===>>> StepEvent@nsk.jdi.BScenarios.hotswap.tc05x002a:64 in thread main
      event info: #2
      thread - main
      source - tc05x002a.java
      method - method_B
      line - 64
      !!!Expected step event!!!

      debugee.stderr> method_C:: line 1
      debugee.stderr> method_C:: line 2
      debugee.stderr> method_C:: line 3
      debugee.stderr> method_C:: line 4
      =============
      TEST FINISHES

      Timeout refired 480 times
      ----------System.err:(0/0)----------
      ----------rerun:(36/5614)*----------

      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): 522.426

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated: