-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8364280: NMTCommittedVirtualMemoryTracker.test_committed_virtualmemory_region_vm fails with assertion "negative distance" #26689
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
Conversation
…y_region_vm fails with assertion "negative distance"
|
👋 Welcome back azafari! A progress list of the required criteria for merging this PR into |
|
@afshin-zafari 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 46 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 |
|
@afshin-zafari 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. |
Webrevs
|
|
LGTM, thanks for fixing this! |
|
Thank you @jdksjolen and @gerard-ziemski for your reviews. |
|
Going to push as commit db12f19.
Your commit was automatically rebased without conflicts. |
|
@afshin-zafari Pushed as commit db12f19. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The VirtualMemoryTracker API uses a tree internally for tracking the memory regions and their states/info. This tree should not be changed when looking for some regions. If not synch'ed, the nodes in the tree may change meanwhile and the retrieved info are not as expected. The unit test in this PR did not synch these looking up with VMT. The corresponding lock is used to address the problem.
Tests:
local: linux-x64-debug NMTGtests
mach5: tiers 1-5, {macosx-aarch64, linux-x64, windows-x64} x {debug, release}
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26689/head:pull/26689$ git checkout pull/26689Update a local copy of the PR:
$ git checkout pull/26689$ git pull https://git.openjdk.org/jdk.git pull/26689/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26689View PR using the GUI difftool:
$ git pr show -t 26689Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26689.diff
Using Webrev
Link to Webrev Comment