-
Notifications
You must be signed in to change notification settings - Fork 6.3k
8350704: Create tests to ensure the failure behavior of core reflection APIs #23788
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 liach! A progress list of the required criteria for merging this PR into |
@liach 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 140 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
|
The code of the tests look fine and of it itself; however, I think the test files should get some more comments describing in more details what and how the test is checking what it is testing. |
Added comments and reran "jdk/java/lang/Class jdk/java/lang/annotation jdk/java/lang/reflect/Generics" tests. |
Thanks for the reviews! /integrate |
Going to push as commit a449aee.
Your commit was automatically rebased without conflicts. |
Core reflection's generic signature parsing system is used for many aspects, including annotations and enclosing methods, yet it is under-tested. It is better for us to set up tests to ensure that sensitive error behaviors of core reflection remain the same across implementation updates, such as #19281.
This patch also includes a JUnit converted version of #22581 (comment) test checking behavior around annotations with duplicate interfaces. Interesting that this causes failure in class, field, and methods (constructors), but not in parameters.
Testing: jdk-tier 1, jdk-tier 2
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23788/head:pull/23788
$ git checkout pull/23788
Update a local copy of the PR:
$ git checkout pull/23788
$ git pull https://git.openjdk.org/jdk.git pull/23788/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23788
View PR using the GUI difftool:
$ git pr show -t 23788
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23788.diff
Using Webrev
Link to Webrev Comment