Skip to content

Conversation

@shipilev
Copy link
Member

@shipilev shipilev commented Jun 4, 2025

SonarCloud points out that ThreadLock class introduced by JDK-8357650 can be turned into static nested class. I don't think this shows any real bug yet, as unreferenced enclosing class reference gets nowhere. But it would be nice to be extra crisp here.

Additional testing:

  • Linux x86_64 server fastdebug, serviceability/
  • Linux x86_64 server fastdebug, jdk_management

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-8358588: ThreadSnapshot.ThreadLock should be static nested class (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25638

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jun 4, 2025

👋 Welcome back shade! 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
Copy link

openjdk bot commented Jun 4, 2025

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

8358588: ThreadSnapshot.ThreadLock should be static nested class

Reviewed-by: alanb, sspitsyn, amenkov

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

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 openjdk bot added the rfr Pull request is ready for review label Jun 4, 2025
@openjdk
Copy link

openjdk bot commented Jun 4, 2025

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

  • core-libs

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.

@openjdk openjdk bot added the core-libs core-libs-dev@openjdk.org label Jun 4, 2025
@mlbridge
Copy link

mlbridge bot commented Jun 4, 2025

Webrevs

@AlanBateman
Copy link
Contributor

/label remove core-libs
/label add serviceability

Copy link
Contributor

@AlanBateman AlanBateman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not an issue but clearer to define it as a static class.

(I've fixed the labels on this PR as this is serviceability code).

@openjdk openjdk bot removed the core-libs core-libs-dev@openjdk.org label Jun 4, 2025
@openjdk
Copy link

openjdk bot commented Jun 4, 2025

@AlanBateman
The core-libs label was successfully removed.

@openjdk openjdk bot added ready Pull request is ready to be integrated serviceability serviceability-dev@openjdk.org labels Jun 4, 2025
@openjdk
Copy link

openjdk bot commented Jun 4, 2025

@AlanBateman
The serviceability label was successfully added.

@AlanBateman
Copy link
Contributor

The tests in test/jdk/com/sun/management/HotSpotDiagnosticMBean is the quickest way to exercise this code.

@shipilev
Copy link
Member Author

shipilev commented Jun 4, 2025

The tests in test/jdk/com/sun/management/HotSpotDiagnosticMBean is the quickest way to exercise this code.

Thanks! I just ran the entire jdk_management test group without any problems.

@shipilev
Copy link
Member Author

shipilev commented Jun 5, 2025

Thank you! Here goes.

/integrate

@openjdk
Copy link

openjdk bot commented Jun 5, 2025

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

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jun 5, 2025
@openjdk openjdk bot closed this Jun 5, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jun 5, 2025
@openjdk
Copy link

openjdk bot commented Jun 5, 2025

@shipilev Pushed as commit dc94900.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integrated Pull request has been integrated serviceability serviceability-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

4 participants