-
Notifications
You must be signed in to change notification settings - Fork 6.3k
8304811: vmTestbase/vm/mlvm/indy/func/jvmti/stepBreakPopReturn/INDIFY_Test.java fails with JVMTI_ERROR_TYPE_MISMATCH #27598
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 amenkov! A progress list of the required criteria for merging this PR into |
@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 11 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 |
@alexmenkov To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command. Applicable Labels
|
/label add serviceability |
@alexmenkov |
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.
The fix looks reasonable.
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.
I agree this seems reasonable. Though I still wonder why this suddenly started appearing only on linux-aarch64.
Thanks for the quick fix.
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 is good. Thank you for fixing!
Thank you for the review |
Going to push as commit 854b384.
Your commit was automatically rebased without conflicts. |
@alexmenkov Pushed as commit 854b384. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The change fixes the test which intermittently fails.
The test requests MethodEntry. SingleStep and Breakpoint events globally (from all threads).
MethodEntry handler checks location (to be expected test method);
Breakpoint request specifies location in the testes method, only test threads calls the method;
SingleStep handler has no checks for thread or location. So once SingleStep event is enabled, event from other thread can be posted first (or several events from different threads).
The fix enables SingleStep event only for test thread (we get it in MethodEntry)
testing: tier3
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27598/head:pull/27598
$ git checkout pull/27598
Update a local copy of the PR:
$ git checkout pull/27598
$ git pull https://git.openjdk.org/jdk.git pull/27598/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27598
View PR using the GUI difftool:
$ git pr show -t 27598
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27598.diff
Using Webrev
Link to Webrev Comment