-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8325456: Rename nsk_mutex.h #17762
8325456: Rename nsk_mutex.h #17762
Conversation
👋 Welcome back kbarrett! A progress list of the required criteria for merging this PR into |
@kimbarrett The following label will be automatically applied to this pull request:
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. |
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.
I just had a look at this and the way the file nsk/jvmti/scenarios/events/EM04/em04t001/libem04t001.cpp includes nsk_mutex.cpp is consistent with how it includes other cpp files so not worth changing (ie. deleting this) without more rewriting.
The rename change looks good and is trivial.
@kimbarrett 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 9 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
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.
Is it worth renaming the included cpp file to hpp as well? Just a small comment
Nevermind, I missed Coleen's comment |
Thanks for the review, @coleenp and @TheShermanTanker . That seems to be a fairly common pattern in tests. There's a "library" source |
/integrate |
Going to push as commit 10beb31.
Your commit was automatically rebased without conflicts. |
@kimbarrett Pushed as commit 10beb31. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this trivial change that renames the file
test/hotspot/jtreg/vmTestbase/nsk/share/native/nsk_mutex.h to nsk_mutex.hpp.
Testing: mach5 tier1
The usage is odd. The header is only included by the associated .cpp file.
That .cpp file is included by only one other file, and that file is compiled.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17762/head:pull/17762
$ git checkout pull/17762
Update a local copy of the PR:
$ git checkout pull/17762
$ git pull https://git.openjdk.org/jdk.git pull/17762/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17762
View PR using the GUI difftool:
$ git pr show -t 17762
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17762.diff
Webrev
Link to Webrev Comment