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

[TESTBUG] hotspot test_env.sh can set VM_CPU incorrectly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: hotspot
    • Subcomponent:
    • Resolved In Build:
      b89

      Backports

        Description

        Some tests, like Test8017498.sh, depend on VM_CPU being set correctly. VM_CPU is based on running "grep" on the output of -Xinternalversion. The problem is the internal version contains other information that can be mistaken for a cpu name. For example, a JPRT build has an internal version with the format <job id>.<username>.<repo name>, so you can easily get test failures if your username or repo name contain a string that test_env.sh is grepping for. Looks like the same problem exists for VM_OS and VM_TYPE.

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                iklam Ioi Lam
                Reporter:
                dlong Dean Long
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: