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

sun/tools tests can intermittently fail to find app's Java pid

    Details

    • Subcomponent:
    • Resolved In Build:
      b47
    • CPU:
      generic
    • OS:
      windows

      Backports

        Description

        The following SDK/JDK sun/tools tests intermittently fail:

            sun/tools/common/CommonTests.sh
            sun/tools/jmap/Basic.sh
            sun/tools/jstack/Basic.sh

        Here is the URL for the failing config in the 2010.08.13 nightly:

        http://sqeweb.sfbay/nfs/tools/gtee/results/JDK7/NIGHTLY/VM/2010-08-13/RT_Baseline/javase/windows-amd64/server/comp/windows-amd64_javase_server_comp_JT_JDK_sun_tools/analysis.html

        The failure mode looks like:

        INFO: waiting for XXXApplication to initialize...
        INFO: MKS shell pid=143500; Java pid=
        INFO: killing 143500
        ----------System.err:(1/39)----------
        ERROR: could not find app's Java pid.
        result: Failed. Execution failed: exit code 2


        test result: Failed. Execution failed: exit code 2


        The CommonTests.jtr file shows the following environment info:

        ----------System.out:(36/1622)----------
        INFO: JAVA=C:/local/common/jdk/baseline/windows-amd64/bin/java
        INFO: 'C:/local/common/jdk/baseline/windows-amd64/bin/java' is executable.
        INFO: JHAT=C:/local/common/jdk/baseline/windows-amd64/bin/jhat
        INFO: 'C:/local/common/jdk/baseline/windows-amd64/bin/jhat' is executable.
        INFO: JINFO=C:/local/common/jdk/baseline/windows-amd64/bin/jinfo
        INFO: 'C:/local/common/jdk/baseline/windows-amd64/bin/jinfo' is executable.
        INFO: JMAP=C:/local/common/jdk/baseline/windows-amd64/bin/jmap
        INFO: 'C:/local/common/jdk/baseline/windows-amd64/bin/jmap' is executable.
        INFO: JPS=C:/local/common/jdk/baseline/windows-amd64/bin/jps
        INFO: 'C:/local/common/jdk/baseline/windows-amd64/bin/jps' is executable.
        INFO: JSTACK=C:/local/common/jdk/baseline/windows-amd64/bin/jstack
        INFO: 'C:/local/common/jdk/baseline/windows-amd64/bin/jstack' is executable.
        INFO: flag isCygwin=false
        INFO: flag isMKS=false
        INFO: flag isLinux=false
        INFO: flag isSolaris=false
        INFO: flag isUnknownOS=false
        INFO: flag isWindows=true
        INFO: PATTERN_EOL=0000000000 [
         ] hotspot.log $
         
         0000000007
        INFO: PATTERN_EOL works for regular line with grep.
        INFO: PATTERN_EOL works for CR line with grep.
        INFO: PATTERN_EOL works for regular line with sed.
        INFO: PATTERN_EOL works for CR line with sed.
        INFO: PATTERN_WS=0000000000 [ ]
         
         0000000006
        INFO: PATTERN_WS works for blanks with grep.
        INFO: PATTERN_WS works for tabs with grep.
        INFO: PATTERN_WS works for blanks with sed.
        INFO: PATTERN_WS works for tabs with sed.
        INFO: waiting for SleeperApplication to initialize...
        INFO: MKS shell pid=143500; Java pid=
        INFO: killing 143500


        The only strange thing is that isWindows is true, but neither
        isCygwin or isMKS is true. The startApplication() function isn't
        issuing enough debug information to figure out why the app's
        Java pid couldn't be found.
        The Win-AMD64 Server VM -Xcomp config failed these tests in the
        2010.08.13 nightly. The Win-AMD64 Server VM -Xmixed config did
        not fail these tests in the 2010.08.13 nightly.

        In the 2010.08.14 nightly, the Win-AMD64 Server VM -Xmixed config
        failed these tests and one additional test:

            sun/tools/jinfo/Basic.sh

        Here is the URL for that config:

        http://sqeweb.sfbay/nfs/tools/gtee/results/JDK7/NIGHTLY/VM/2010-08-14/RT_Baseline/javase/windows-amd64/server/mixed/windows-amd64_javase_server_mixed_JT_JDK_sun_tools/analysis.html

        In the 2010.08.14 nightly, the Win-AMD64 Server VM -Xcomp config
        did not complete.
        Here is an instance of this failure mode in the Win32 Server VM -Xmixed
        config:

        http://sqeweb.sfbay/nfs/tools/gtee/results/JDK7/NIGHTLY/VM/2010-08-16/RT_Baseline/javase/windows-i586/server/mixed/windows-i586_javase_server_mixed_JT_JDK_sun_tools/analysis.html

        And an instance in the Win32 Server VM -Xcomp config:

        http://sqeweb.sfbay/nfs/tools/gtee/results/JDK7/NIGHTLY/VM/2010-08-16/RT_Baseline/javase/windows-i586/server/comp/windows-i586_javase_server_comp_JT_JDK_sun_tools/analysis.html

        The interesting thing here is that the test machine's platform
        is really Win-ADM64:

        Platform: windows-amd64 VM Arch: windows-i586
        Machine: VM-X4100-07 Info: Windows_NT VM-X4100-07 6 00 8664

        and

        Platform: windows-amd64 VM Arch: windows-i586
        Machine: VM-X4100-07 Info: Windows_NT VM-X4100-07 6 00 8664
        This bug can also affect the following SDK/JDK Logging tests:

            java/util/logging/AnonLoggerWeakRefLeak.sh
            java/util/logging/LoggerWeakRefLeak.sh

        Here is the URL for a failure instance in the 2010.08.19 nightly:

        http://sqeweb.sfbay/nfs/tools/gtee/results/JDK7/NIGHTLY/VM/2010-08-19/RT_Baseline/javase/windows-amd64/server/mixed/windows-amd64_javase_server_mixed_JT_JDK_java_util_logging/analysis.html

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ykantser Yekaterina Kantserova (Inactive)
                  Reporter:
                  dcubed Daniel Daugherty
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Imported:
                    Indexed: