-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8366264: tools/javac/launcher/SourceLauncherStackTraceTest.java does not cover the scenario for 8362237 #26993
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
8366264: tools/javac/launcher/SourceLauncherStackTraceTest.java does not cover the scenario for 8362237 #26993
Conversation
…not cover the scenario for 8362237
👋 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 10 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.
Looks sensible to me. Please be sure to run tests before integrating.
Is there any test I should run besides the |
Since I cannot think of other tests to run and the revised SourceLauncherTest passes on CI against 26 build 13, I think we are fine. Thanks for the reviews. /integrate |
Going to push as commit 0e73993.
Your commit was automatically rebased without conflicts. |
In #26601, I moved a test case to create a traceless exception for the source launcher that depended on C2 behaviors to a separate test with compiler flags. However, that move is incorrect: to reproduce the issue, the cause exception must have no trace while the InvocationTargetException does. My migrated test blindly turned off stack traces for all exceptions, which is not the intended scenario.
I found that in Java 7, Throwable, Exception, Error, and RuntimeException get new constructors that allow specifying suppression and trace filling behaviors. We can use that constructor to prohibit stack traces for the cause while preserving the trace for the InvocationTargetException.
Testing: Running the single source file on Java 24 and getting the array copy IAE (ensure it is a valid reproducer), and running the test to ensure the new case passes.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26993/head:pull/26993
$ git checkout pull/26993
Update a local copy of the PR:
$ git checkout pull/26993
$ git pull https://git.openjdk.org/jdk.git pull/26993/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26993
View PR using the GUI difftool:
$ git pr show -t 26993
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26993.diff
Using Webrev
Link to Webrev Comment