8300339: Run jtreg in the work dir

[magicus]

We had a test setup failure in our distributed test system where the process running jtreg crashed. This caused the hs_err file to end up in the root of the source tree. Dropping crash files in the source tree is bad practice and makes it harder to find such files. We should change the current working directory to the work/output dir before launching jtreg to help avoid this situation in the future.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8300339: Run jtreg in the work dir (Bug - P4)

Reviewers

• Erik Joelsson (@erikj79 - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24452/head:pull/24452
$ git checkout pull/24452

Update a local copy of the PR:
$ git checkout pull/24452
$ git pull https://git.openjdk.org/jdk.git pull/24452/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 24452

View PR using the GUI difftool:
$ git pr show -t 24452

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24452.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back ihse! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@magicus This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8300339: Run jtreg in the work dir

Reviewed-by: erikj

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 60 new commits pushed to the master branch:

• 3cbe686: 8348967: Deprecate security permission classes for removal
• 4645ddb: 8341976: C2: use_mem_state != load->find_exact_control(load->in(0)) assert failure
• 58ff36f: 8350705: [JMH] test security.SSLHandshake failed for 2 threads configuration
• ... and 57 more: https://git.openjdk.org/jdk/compare/3cc43b3224efdf1a3f35fff58b993027a9e1f4ad...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@magicus The following label will be automatically applied to this pull request:

• build

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 02: Full - Incremental (a819d701)
• 01: Full - Incremental (90a76851)
• 00: Full (d2bbfe3a)

[magicus]

/integrate

[openjdk]

Going to push as commit bd73a06.
Since your change was applied there have been 61 commits pushed to the master branch:

• b98d6ae: 8339527: Adjust threshold for MemorySegment::fill native invocation
• 3cbe686: 8348967: Deprecate security permission classes for removal
• 4645ddb: 8341976: C2: use_mem_state != load->find_exact_control(load->in(0)) assert failure
• ... and 58 more: https://git.openjdk.org/jdk/compare/3cc43b3224efdf1a3f35fff58b993027a9e1f4ad...master

Your commit was automatically rebased without conflicts.

[openjdk]

@magicus Pushed as commit bd73a06.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.