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

test/sun/management/jmxremote/startstop/JMXStartStopTest.sh failing again

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P3 P3
    • tbd
    • 8
    • core-svc


      Historically, this test has been problematic and has been re-worked at least once to make it more reliable.

      It is still failing intermittently (but very rarely) in JPRT and in local test runs. The sample is sample output from a failure. Note that the machine is unload load at the time of the failure, this may or may not be factor here.

      #Test Results (version 2)
      #Sun Jun 16 00:12:58 IST 2013
      #checksum:6c08ff2dc28fdd52
      #-----testdescription-----
      $file=/u/alanb/ws/tl/jdk/test/sun/management/jmxremote/startstop/JMXStartStopTest.sh
      $root=/u/alanb/ws/tl/jdk/test
      keywords=bug7110104 shell
      run=USER_SPECIFIED build JMXStartStopTest JMXStartStopDoSomething\nUSER_SPECIFIED shell JMXStartStopTest.sh --jtreg --no-compile\n
      source=JMXStartStopTest.sh
      title=No word Failed expected in the test output

      #-----environment-----

      #-----testresult-----
      description=file\:/u/alanb/ws/tl/jdk/test/sun/management/jmxremote/startstop/JMXStartStopTest.sh
      elapsed=15993 0\:00\:15.993
      end=Sun Jun 16 00\:12\:58 IST 2013
      environment=regtest
      execStatus=Failed. Execution failed\: exit code 2
      hostname=ashtown.ie.oracle.com
      javatestOS=Linux 3.2.0-23-generic (amd64)
      javatestVersion=4.4
      jtregVersion=jtreg 4.1 dev b00
      script=com.sun.javatest.regtest.RegressionScript
      sections=script_messages build compile shell
      start=Sun Jun 16 00\:12\:42 IST 2013
      test=sun/management/jmxremote/startstop/JMXStartStopTest.sh
      user.name=albatem
      work=/u/alanb/testing/jtreg/JTwork/sun/management/jmxremote/startstop

      #section:script_messages
      ----------messages:(5/271)----------
      JDK under test: (/u/alanb/ws/tl/build/linux-x86_64-normal-server-release/images/j2sdk-image)
      java version "1.8.0-internal"
      Java(TM) SE Runtime Environment (build 1.8.0-internal-albatem_2013_06_08_08_40-b00)
      Java HotSpot(TM) 64-Bit Server VM (build 25.0-b34, mixed mode)


      #section:build
      ----------messages:(3/169)----------
      command: build JMXStartStopTest JMXStartStopDoSomething
      reason: User specified action: run build JMXStartStopTest JMXStartStopDoSomething
      elapsed time (seconds): 0.101
      result: Passed. Build successful

      #section:compile
      ----------messages:(3/293)----------
      command: compile -XDignore.symbol.file=true /u/alanb/ws/tl/jdk/test/sun/management/jmxremote/startstop/JMXStartStopTest.java /u/alanb/ws/tl/jdk/test/sun/management/jmxremote/startstop/JMXStartStopDoSomething.java
      reason: .class file out of date or does not exist
      elapsed time (seconds): 0.101
      ----------direct:(2/175)----------
      Note: /u/alanb/ws/tl/jdk/test/sun/management/jmxremote/startstop/JMXStartStopTest.java uses unchecked or unsafe operations.
      Note: Recompile with -Xlint:unchecked for details.
      result: Passed. Compilation successful

      #section:shell
      ----------messages:(3/173)----------
      command: shell JMXStartStopTest.sh [--jtreg, --no-compile]
      reason: User specified action: run shell JMXStartStopTest.sh --jtreg --no-compile
      elapsed time (seconds): 15.892
      ----------System.out:(3/115)----------
      **** Test one ****
      Waiting JMXStartStopDoSomething to start: 0
      Failed r1(OK):OK_CONN r2(NO):NO_CONN r3(OK):NO_CONN
      ----------System.err:(1/110)----------
      /u/alanb/ws/tl/jdk/test/sun/management/jmxremote/startstop/JMXStartStopTest.sh: 109: exit: Illegal number: -1
      result: Failed. Execution failed: exit code 2


      test result: Failed. Execution failed: exit code 2

            jbachorik Jaroslav BachorĂ­k
            alanb Alan Bateman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: