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
8255225: compiler/aot tests fail on Windows with NPE during artifact resolution #800
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
@shipilev To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command. Applicable Labels
|
/label build |
@shipilev |
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, thanks for fixing it!
@shipilev 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 22 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 |
Thanks @erikj79! I want this fixed sooner, is it OK to push now? Or should we ask someone else to review too? |
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. Thanks for fixing it. I saw it in our CI as well.
/integrate |
@shipilev Since your change was applied there have been 26 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 64dc4b1. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Bisection shows it started to happen after JDK-8253660. I believe
toString()
there is not very resilient in the face ofnull
causes.Example output:
...and since it is a part of this block:
...we never actually get to
// let jaotc try to find linker
part, and that is why I suspect it causes Windows x86_64 tier1/compiler failures in GitHub workflows. See below,Windows tier1/compiler
tests are now passing. (There are some infra failures in other places on Windows, though).Progress
Testing
Failed test task
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/800/head:pull/800
$ git checkout pull/800