8278065: Refactor subclassAudits to use ClassValue

[rkennke]

This backports the fix for JDK-8278065, which fixes a number of small issues with the preceding change for JDK-8277072.
The original change has baked for several weeks in jdk19 and applies with some conflicts caused by different context.

Testing:

• tier1
• tier2
• tier3

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8278065: Refactor subclassAudits to use ClassValue

Reviewers

• Roger Riggs (@RogerRiggs - Reviewer) ⚠️ Review applies to 702abdf
• Peter Levart (@plevart - Reviewer) ⚠️ Review applies to 702abdf

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/899/head:pull/899
$ git checkout pull/899

Update a local copy of the PR:
$ git checkout pull/899
$ git pull https://git.openjdk.java.net/jdk11u-dev pull/899/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 899

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/899.diff

[bridgekeeper]

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

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 02: Full (7b9e6422)
• 01: Full - Incremental (702abdfd)
• 00: Full (702abdfd)

[rkennke]

@RogerRiggs @plevart If you find some time, could you please review this backport? Thank you!

[GoeLin]

Pre-submit failures; gcc issues, unrelated.

[plevart]

Looks good.

[openjdk-notifier]

The dependent pull request has now been integrated, and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout rkennke-backport-8eb453ba
git fetch https://git.openjdk.java.net/jdk11u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

@rkennke this pull request can not be integrated into master due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:

git checkout backport-JDK-8278065
git fetch https://git.openjdk.java.net/jdk11u-dev master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

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

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

8278065: Refactor subclassAudits to use ClassValue

Reviewed-by: rriggs, plevart

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

[rkennke]

/integrate

[openjdk]

Going to push as commit 01c4d3f.
Since your change was applied there has been 1 commit pushed to the master branch:

• b1f18cb: 8280041: Retry loop issues in java.io.ClassCache

Your commit was automatically rebased without conflicts.

[openjdk]

@rkennke Pushed as commit 01c4d3f.

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