8343809: Add requires tag to mark tests that are incompatible with exploded image

[lmesnik]

The
jdk.explodedImage
might be used to filter tests incompatible with
make exploded-run-test TEST=...

The exploded-run-test mode is used only for quick manual testing and not in CI or ATR testing. However, it is make sense to reduce false positive failures so developers don't waste time during local testing.

---

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-8343809: Add requires tag to mark tests that are incompatible with exploded image (Enhancement - P4)

Reviewers

• David Holmes (@dholmes-ora - Reviewer) Review applies to 9be434fa
• Alan Bateman (@AlanBateman - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28814

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8343809: Add requires tag to mark tests that are incompatible with exploded image

Reviewed-by: alanb, dholmes

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

• d9bd300: 8374382: (aio) AsynchronousFileChannel writes wrong content using heap ByteBuffer when position != 0
• 752f46d: 8374373: Typo in VirtualThreadSchedulerMXBean.setParallelism javadoc
• 96e5c27: 8373893: Refactor networking http server tests to use JUnit
• ... and 158 more: https://git.openjdk.org/jdk/compare/23c39757ecdc834c631f98f4487cfea21c9b948b...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]

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

• hotspot

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

• 01: Full - Incremental (591c1eb7)
• 00: Full (9be434fa)

[dholmes-ora]

Seems reasonable.

Thanks

[lmesnik]

ping

[lmesnik]

/integrate

[openjdk]

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

• 2daf12e: 8374465: Spurious dot in documentation for JVMTI ClassLoad
• 3439512: 8374317: Change GCM IV size to 12 bytes when encrypting/decrypting TLS session ticket
• efb79dc: 8374444: Fix simple -Wzero-as-null-pointer-constant warnings
• ... and 164 more: https://git.openjdk.org/jdk/compare/23c39757ecdc834c631f98f4487cfea21c9b948b...master

Your commit was automatically rebased without conflicts.

[openjdk]

@lmesnik Pushed as commit 53824cf.

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