-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
JDK-8305414: gtest/NMTGtests.java is failing various sub-tests #13296
JDK-8305414: gtest/NMTGtests.java is failing various sub-tests #13296
Conversation
👋 Welcome back stuefe! A progress list of the required criteria for merging this PR into |
Webrevs
|
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.
Looks good to me. Thanks!
Thank you for the quick review! |
@tstuefe 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 82 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 |
…g-various-sub-tests
…g-various-sub-tests
…g-various-sub-tests
…s-failing-various-sub-tests
Pinging @jdksjolen ... |
Friendly ping |
@tstuefe - I'm running Mach5 testing on v04. Will keep you posted:
I'm done with the Mach5 testing. Looks good to me. |
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.
Looks good to me to.
Thank you @adinn . Thanks to @dcubed-ojdk for testing. /integrate |
Going to push as commit fb9a29d.
Your commit was automatically rebased without conflicts. |
With JDK-8304815 we started to use NMT - if enabled - for better hs-err reporting by asking it to make sense out of otherwise unknown memory locations.
If the location points into or nearby a C-heap block, we now see that. That even works for dead blocks (use after free). For details, see JDK-8304815 and the comments in mallocTracker.cpp.
The change came with its own gtest, which promptly started to fail on some platforms. The reason was an error in MallocTracker::print_pointer_information() that caused us to prematurely return from its search-loop if we encounter unmapped memory. Never happened in my tests, but of course depends on where libc places the test blocks, which makes this error intermittent.
Patch fixes that, and also fixes some debug output in the test.
Tests: Ran the test manually on Linux aarch64; was able to reproduce the errors without patch, no errors with patch.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/13296/head:pull/13296
$ git checkout pull/13296
Update a local copy of the PR:
$ git checkout pull/13296
$ git pull https://git.openjdk.org/jdk.git pull/13296/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 13296
View PR using the GUI difftool:
$ git pr show -t 13296
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13296.diff
Webrev
Link to Webrev Comment