-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8283597: [REDO] Invalid generic signature for redefined classes #8007
Conversation
👋 Welcome back amenkov! A progress list of the required criteria for merging this PR into |
@alexmenkov The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
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.
It is nice you've found the root cause of this regression!
Thanks,
Serguei
@alexmenkov 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 95 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.
Yes, this looks good, not that I understand the inner workings of jtreg. All but two tests in that directory don't @compile the test case.
/integrate |
Going to push as commit 0cd46f6.
Your commit was automatically rebased without conflicts. |
@alexmenkov Pushed as commit 0cd46f6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
After pushing fix for JDK-8282241 (#7676) random tests from serviceability/jvmti/RedefineClasses start to fail with
java.lang.NoClassDefFoundError: jdk/test/lib/helpers/ClassFileInstaller$Manifest
This is caused by JTReg classpath directories sharing between tests.
Research shown that the issue was caused by using
run compile -g RedefineGenericSignatureTest.java
in the test to include additional debug info.
Actually "-g" it's not needed as the test only needs source file data and it's included by default.
The fix is the same as previous one, the only difference is in the test:
Tested with debug and release builds, 1500 runs without failures.
@coleenp , @sspitsyn : could you please re-review the fix
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8007/head:pull/8007
$ git checkout pull/8007
Update a local copy of the PR:
$ git checkout pull/8007
$ git pull https://git.openjdk.java.net/jdk pull/8007/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8007
View PR using the GUI difftool:
$ git pr show -t 8007
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8007.diff