-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8358588: ThreadSnapshot.ThreadLock should be static nested class #25638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8358588: ThreadSnapshot.ThreadLock should be static nested class #25638
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
|
@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: 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
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 |
|
/label remove core-libs |
AlanBateman
left a comment
There was a problem hiding this 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).
|
@AlanBateman |
|
@AlanBateman |
|
The tests in test/jdk/com/sun/management/HotSpotDiagnosticMBean is the quickest way to exercise this code. |
Thanks! I just ran the entire |
|
Thank you! Here goes. /integrate |
|
Going to push as commit dc94900.
Your commit was automatically rebased without conflicts. |
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:
serviceability/jdk_managementProgress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25638/head:pull/25638$ git checkout pull/25638Update a local copy of the PR:
$ git checkout pull/25638$ git pull https://git.openjdk.org/jdk.git pull/25638/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25638View PR using the GUI difftool:
$ git pr show -t 25638Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25638.diff
Using Webrev
Link to Webrev Comment