8317039 Enable specifying the JDK used to run jtreg

[LudwikJaniuk]

This pull request introduces changes in the build makefiles necessary to enable the user to specify a jdk to use when launching jtreg. It introduces a new configure flag, --with-jtreg-jdk, which takes a JDK path similar to the already existing --with-boot-jdk.

Before this pull request, boot-jdk was always used to launch jtreg. This pull request decouples the two, but still defaults to boot-jdk if no value is specified.

---

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-8317039: Enable specifying the JDK used to run jtreg (Enhancement - P4)

Reviewers

• Erik Joelsson (@erikj79 - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 16010

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back lujaniuk! 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]

@LudwikJaniuk 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 (1dbc37ce)
• 01: Full - Incremental (24bfd496)
• 00: Full (c9f7dd25)

[LudwikJaniuk]

I've addressed the comments left by @erikj79 so far.

[openjdk]

@LudwikJaniuk 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:

8317039: Enable specifying the JDK used to run jtreg

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 48 new commits pushed to the master branch:

• 3bcfac1: 8317246: Cleanup java.net.URLEncoder and URLDecoder use of file.encoding property
• b6a97c0: 8316880: AArch64: "stop: Header is not fast-locked" with -XX:-UseLSE since JDK-8315880
• 287b243: 8316893: Compile without -fno-delete-null-pointer-checks
• 26c21f5: 8314294: Unsafe::allocateMemory and Unsafe::freeMemory are slower than malloc/free
• 6e1aacd: 8296631: NSS tests failing on OL9 linux-aarch64 hosts
• d2e2c4c: 8309667: TLS handshake fails because of ConcurrentModificationException in PKCS12KeyStore.engineGetEntry
• e25121d: 8316929: Shenandoah: Shenandoah degenerated GC and full GC need to cleanup old OopMapCache entries
• 5c8366e: 8268622: Performance issues in javac Name class
• ad81abd: 8317034: Remove redundant type cast in the java.util.stream package
• d7d1d42: 8316771: Krb5.java has not defined messages for all error codes
• ... and 38 more: https://git.openjdk.org/jdk/compare/fc98998627443d6e73ac70661f47f48b30525712...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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@erikj79) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[LudwikJaniuk]

/integrate

[openjdk]

@LudwikJaniuk
Your change (at version 1dbc37c) is now ready to be sponsored by a Committer.

[dholmes-ora]

/sponsor

[openjdk]

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

• 1ed9c76: 8309204: Obsolete DoReserveCopyInSuperWord
• 3630af2: 8316594: C2 SuperWord: wrong result with hand unrolled loops
• c6c69b5: 8314654: Metaspace: move locking out of MetaspaceArena
• 3105538: 8316146: Open some swing tests 4
• 36314a9: 8267509: Improve IllegalAccessException message to include the cause of the exception
• ddacf92: 8305765: CompressedClassPointers.java is unreliable due to ASLR
• 4195246: 8317354: Serial: Move DirtyCardToOopClosure to gc/serial folder
• 0a3a925: 8316414: C2: large byte array clone triggers "failed: malformed control flow" assertion failure on linux-x86
• b0d6c84: 8316396: Endless loop in C2 compilation triggered by AddNode::IdealIL
• a8549b6: 8280120: [IR Framework] Add attribute to @ir to enable/disable IR matching based on the architecture
• ... and 65 more: https://git.openjdk.org/jdk/compare/fc98998627443d6e73ac70661f47f48b30525712...master

Your commit was automatically rebased without conflicts.

[openjdk]

@dholmes-ora @LudwikJaniuk Pushed as commit a250ae4.

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