-
Notifications
You must be signed in to change notification settings - Fork 164
8222323: ChildAlwaysOnTopTest.java fails with "RuntimeException: Failed to unset alwaysOnTop" #378
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
👋 Welcome back kurashige23! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
Webrevs
|
@kurashige23 This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
@kurashige23 This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the |
/open |
@kurashige23 This pull request is now open |
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.
Seems OK.
Please ask for approval of the bug using the |
/approval JDK-8021961 request Test-only backport, no risk. |
@kurashige23 This issue is not associated with this pull request. |
/approval 377 request Test-only backport, no risk. |
@kurashige23 This issue is not associated with this pull request. |
/approval request Test-only backport, no risk. |
@kurashige23 |
This PR has been approved, please add /integrate. |
This needs #377 first. |
The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout AlwaysOnTop_8222323
git fetch https://git.openjdk.org/jdk8u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
|
@kurashige23 This change now passes all automated pre-integration checks. 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 32 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@jerboaa) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/sponsor |
@phohensee The change author (@kurashige23) must issue an |
/integrate |
@kurashige23 |
/sponsor |
Going to push as commit b05e679.
Your commit was automatically rebased without conflicts. |
@phohensee @kurashige23 Pushed as commit b05e679. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi,
This is a backport of JDK-8222323: ChildAlwaysOnTopTest.java fails with "RuntimeException: Failed to unset alwaysOnTop"
Original patch does not apply cleanly to JDK-8021961 applied code, because the fix uses "StringBuffer.isEmpty()" published in JDK15. I fixed the test so as not to use "StringBuffer.isEmpty()".
Testing: jdk_awt on RHEL7, GHA testing
Thanks.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/378/head:pull/378
$ git checkout pull/378
Update a local copy of the PR:
$ git checkout pull/378
$ git pull https://git.openjdk.org/jdk8u-dev.git pull/378/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 378
View PR using the GUI difftool:
$ git pr show -t 378
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/378.diff
Webrev
Link to Webrev Comment