-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8370663: Incorrect synchronization in nsk/jvmti/RedefineClasses when expected events are not received #27992
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
…expected events are not received
|
👋 Welcome back lmesnik! A progress list of the required criteria for merging this PR into |
|
@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 34 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.
This looks okay to me. Thank you for catching it!
|
/integrate |
|
Going to push as commit 2fc4cbe.
Your commit was automatically rebased without conflicts. |
These tests nsk/jvmti/RedefineClasses
redefclass028.cpp
redefclass029.cpp
redefclass030.cpp
try to provoke compilation of certain methds and exit if CompileMethodLoad event are not received
with
exit(95 + PASS)Before exit they also try to resume java using
nsk_jvmti_resumeSync();The java is not suspended so this resume is failing. Currently, the failure is silently ignored now but going to fail after
https://bugs.openjdk.org/browse/JDK-8352654
is fixed. This situation might happen with -Xcomp or other similar flags the might change compilation order. The complete fix would be to understand if we should run test in all modes and have strict check or throw SkippedException. But it requires much more effort.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27992/head:pull/27992$ git checkout pull/27992Update a local copy of the PR:
$ git checkout pull/27992$ git pull https://git.openjdk.org/jdk.git pull/27992/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27992View PR using the GUI difftool:
$ git pr show -t 27992Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27992.diff
Using Webrev
Link to Webrev Comment