-
Notifications
You must be signed in to change notification settings - Fork 5.9k
8294155: Exception thrown before awaitAndCheck hangs PassFailJFrame #23564
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
Conversation
Catch exceptions in Builder.build() and dispose of all the windows if an exception occurs.
👋 Welcome back aivanov! A progress list of the required criteria for merging this PR into |
@aivanov-jdk 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 |
@aivanov-jdk 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. |
/integrate |
Going to push as commit 906358d.
Your commit was automatically rebased without conflicts. |
@aivanov-jdk Pushed as commit 906358d. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
If a manual test throws an exception during construction of
PassFailJFrame
, the test execution hangs. When the builder pattern is used, no UI appears on the screens, but the Java process does not terminate automatically because there are windows which prevent AWT from shutting down.Fix:
Catch exceptions in
PassFailJFrame.Builder.build()
and dispose of all the windows if an exception occurs.This ensures all the created windows are disposed of, which lets AWT shut down cleanly.
Note: the above problem doesn't occur when the test is run with
jtreg
because jtreg shuts down the JVM as soon as the main thread exits.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23564/head:pull/23564
$ git checkout pull/23564
Update a local copy of the PR:
$ git checkout pull/23564
$ git pull https://git.openjdk.org/jdk.git pull/23564/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23564
View PR using the GUI difftool:
$ git pr show -t 23564
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23564.diff
Using Webrev
Link to Webrev Comment