-
Notifications
You must be signed in to change notification settings - Fork 106
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
8320061: [nmt] Multiple issues with peak accounting #481
Conversation
👋 Welcome back Delawen! A progress list of the required criteria for merging this PR into |
@Delawen 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 8 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 As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@shipilev, @tstuefe) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
This backport pull request has now been updated with issue from the original commit. |
Webrevs
|
/clean This is a clean merge to another open PR. |
@Delawen Only OpenJDK Committers can use the |
The parent pull request that this pull request depends on 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 backport-JDK-8320061
git fetch https://git.openjdk.org/jdk21u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
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.
Superficially, this looks good. @tstuefe should ack as well.
Have you ran runtime/NMT
tests with this PR?
/reviewers 2 |
|
Tests are being run on the github jobs right now. Once they are done I will do the approval command. Thanks @shipilev ! |
It would be safer to run |
Sure, then I will run them now :) (I did it on the original PR commit but it's true, a merge that big deserves another try) |
Tests passed. Also I checked again the output of the following commands:
|
/approval JDK-8320061 request Fix Request |
@tstuefe can you take a look here? |
Hi @Delawen, thank you for doing this. Can you describe what parts of the patch you had to adapt, in order to make my review easier? Were the needed changes trivial, e.g. only comments? |
I didn't have to change much, just fixing a couple of trivial merge conflicts (line numbers changed and that made git ask if it was right). It is mostly the original backport. If you compare the original commit and this one you will see the changes shown are the same. |
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.
Thank you!
Thanks, looks good. I wish we had a tool for showing the manual changes after such a merge. |
/integrate |
Thanks both! Let's do this. /sponsor |
Going to push as commit 262cacb.
Your commit was automatically rebased without conflicts. |
This is a follow up of #440
This backport fixes several NMT things, among those, the problem with largest_committed being 0KB as shown on the previous PR.
Example of output:
As described in the original PR, other features in this PR is fixing the scale so it also shows when the allocation value is zero (note the GB now instead of showing KB as before, and the 0GB that is shown):
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/481/head:pull/481
$ git checkout pull/481
Update a local copy of the PR:
$ git checkout pull/481
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/481/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 481
View PR using the GUI difftool:
$ git pr show -t 481
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/481.diff
Webrev
Link to Webrev Comment