-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8253660: Need better error report when artifact resolution fails in AotCompiler.java #368
Conversation
…rint stack trace in AotCotCompiler.
/label build |
👋 Welcome back erikj! A progress list of the required criteria for merging this PR into |
@erikj79 |
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 good to me.
@erikj79 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 306 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 |
/integrate |
@erikj79 Since your change was applied there have been 321 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 0b51016. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
In AotCompiler.java, if artifact resolution fails, we have no way of diagnosing the error. This patch improves the default toString() of ArtifactResolverException to automatically include the toString() method of the root cause. It also adds stack trace printing specifically in AotCompiler.java.
I also found a similar issue in PKCS11Test, and fixed it by adding the ArtifactResolverException there as cause for the RuntimeException being thrown. This causes the stack trace to be printed on failure.
I looked through all other uses of ArtifactResolver, but they are handling the exception in a way that already prints the stack trace.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/368/head:pull/368
$ git checkout pull/368