-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8255031 : Update java/util/prefs/AddNodeChangeListener.java to report more failure info #773
Conversation
👋 Welcome back bchristi! A progress list of the required criteria for merging this PR into |
@bchristi-git The following label will be automatically applied to this pull request:
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. |
Webrevs
|
@bchristi-git 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 48 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 |
@bchristi-git Since your change was applied there have been 65 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 8afdcae. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi,
The java/util/prefs/AddNodeChangeListener.java test fails once in a while in the automated test system. Previous failures were traced to machine configuration errors, but that does not appear to be the case this time.
My efforts to reproduce this failure have been unsuccessful. The only useful information I've gleaned so far from the test failure logs is that the overall duration for running tier1 is longer than usual when the test failure happens.
I would like to make the following updates to the test, in hopes of learning more if and when this test fails again:
Thanks,
-Brent
Progress
Testing
Failed test task
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/773/head:pull/773
$ git checkout pull/773