-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8290468: Remove gc/gctests/mallocWithGC tests #9563
Conversation
👋 Welcome back lmesnik! A progress list of the required criteria for merging this PR into |
/label remove hotspot |
/cc hotspot-gc |
@lmesnik |
@lmesnik |
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.
@lmesnik 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 19 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 |
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.
Lgtm.
/integrate |
Going to push as commit b1817a3.
Your commit was automatically rebased without conflicts. |
The gc/gctests/mallocWithGC tests test interaction of GC with malloc/free.
They are duplicates of vmTestbase/gc/lock/malloc/ tests.
Not sure that even vmTestbase/gc/lock/malloc/ are needed. GC do nothing with malloc/free and it doesn't make sense to test their interaction.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9563/head:pull/9563
$ git checkout pull/9563
Update a local copy of the PR:
$ git checkout pull/9563
$ git pull https://git.openjdk.org/jdk pull/9563/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9563
View PR using the GUI difftool:
$ git pr show -t 9563
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9563.diff