Skip to content

Conversation

liach
Copy link
Member

@liach liach commented Aug 28, 2025

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

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8366264: tools/javac/launcher/SourceLauncherStackTraceTest.java does not cover the scenario for 8362237 (Bug - P4)

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

@bridgekeeper
Copy link

bridgekeeper bot commented Aug 28, 2025

👋 Welcome back liach! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Aug 28, 2025

@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:

8366264: tools/javac/launcher/SourceLauncherStackTraceTest.java does not cover the scenario for 8362237

Reviewed-by: cstein, jlahoda

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 master branch:

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 master branch, type /integrate in a new comment.

@openjdk
Copy link

openjdk bot commented Aug 28, 2025

@liach The following label will be automatically applied to this pull request:

  • compiler

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added compiler compiler-dev@openjdk.org rfr Pull request is ready for review labels Aug 28, 2025
@mlbridge
Copy link

mlbridge bot commented Aug 28, 2025

Webrevs

Copy link
Contributor

@lahodaj lahodaj left a 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.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Aug 29, 2025
@liach
Copy link
Member Author

liach commented Aug 29, 2025

Please be sure to run tests before integrating.

Is there any test I should run besides the tools/javac/launcher/SourceLauncherTest.java?

@liach
Copy link
Member Author

liach commented Aug 30, 2025

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

@openjdk
Copy link

openjdk bot commented Aug 30, 2025

Going to push as commit 0e73993.
Since your change was applied there have been 12 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Aug 30, 2025
@openjdk openjdk bot closed this Aug 30, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Aug 30, 2025
@openjdk
Copy link

openjdk bot commented Aug 30, 2025

@liach Pushed as commit 0e73993.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler compiler-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants