-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8300644: Remove gc/shenandoah/jni/TestStringCriticalWithDedup.java #12089
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
👋 Welcome back eosterlund! 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 like it will also be safe to delete libTestStringCriticalWithDedup.c
.
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
@fisk 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 163 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 |
Ah yeah, look at that. Fixed. |
Thanks for the reviews, @MBaesken and @earthling-amzn! |
/integrate |
Going to push as commit 95fafd0.
Your commit was automatically rebased without conflicts. |
The gc/shenandoah/jni/TestStringCriticalWithDedup.java test was designed to catch failure to pin strings being passed out to JNI critical users, because that used to be dangerous. After JDK-8299673 that is not dangerous any longer. Conversely, now we kind of want deduplication to proceed regardless of JNI critical, which defeats the purpose of this test. It should be removed.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12089/head:pull/12089
$ git checkout pull/12089
Update a local copy of the PR:
$ git checkout pull/12089
$ git pull https://git.openjdk.org/jdk pull/12089/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12089
View PR using the GUI difftool:
$ git pr show -t 12089
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12089.diff