-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8333714: Cleanup the usages of CHECK_EXCEPTION_NULL_FAIL macro in java launcher #19576
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 jpai! A progress list of the required criteria for merging this PR into |
@jaikiran 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 94 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 |
Webrevs
|
Any reviews for this please? |
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, it makes these invokeXXX functions easier to read and avoids any confusion on return NULL vs. pending exception.
Thank you for the review Alan. I'll integrate this in a few hours. |
/integrate |
Going to push as commit efab48c.
Your commit was automatically rebased without conflicts. |
Can I please get a review for this change which proposes to remove the
CHECK_EXCEPTION_NULL_FAIL
macro from thejava
launcher code?This addresses https://bugs.openjdk.org/browse/JDK-8333714. As noted in that JBS issue, in a recent PR discussion, it was suggested #18786 (comment) that this macro should be removed and the failure of a JNI specified operation (the ones for which this macro is being used) should be determined based on a
NULL
value returned from that function. The commit in this PR removes this macros and updates the call sites to do aNULL
check.Given the nature of this change, no new tests have been added. tier1, tier2 and tier3 testing passed successfully with these changes.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19576/head:pull/19576
$ git checkout pull/19576
Update a local copy of the PR:
$ git checkout pull/19576
$ git pull https://git.openjdk.org/jdk.git pull/19576/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 19576
View PR using the GUI difftool:
$ git pr show -t 19576
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19576.diff
Webrev
Link to Webrev Comment