8296083: javax/swing/JTree/6263446/bug6263446.java fails intermittently on a VM

[Rudometov]

Backport for JDK-8296083 javax/swing/JTree/6263446/bug6263446.java fails intermittently on a VM

Original commit openjdk/jdk@dd9aa72

Clean backport.
Test update, low risk.
Test passed during manual run (run in a 50 loop).

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8296083: javax/swing/JTree/6263446/bug6263446.java fails intermittently on a VM

Reviewers

• Goetz Lindenmaier (@GoeLin - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev pull/897/head:pull/897
$ git checkout pull/897

Update a local copy of the PR:
$ git checkout pull/897
$ git pull https://git.openjdk.org/jdk17u-dev pull/897/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 897

View PR using the GUI difftool:
$ git pr show -t 897

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/897.diff

[bridgekeeper]

👋 Welcome back vrudomet! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (28d379ee)

[GoeLin]

LGTM

You may mark changes that only needed a resolve in the ProblemList as /clean.

[openjdk]

@Rudometov 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:

8296083: javax/swing/JTree/6263446/bug6263446.java fails intermittently on a VM

Reviewed-by: goetz

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 1 new commit pushed to the master branch:

• 1c13d7e: 8290839: jdk/jfr/event/compiler/TestJitRestart.java failed with "RuntimeException: No JIT restart event found: expected true, was false"

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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 (@GoeLin) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[Rudometov]

/integrate

[openjdk]

@Rudometov
Your change (at version 28d379e) is now ready to be sponsored by a Committer.

[Rudometov]

Thank you. Unfortunately I do not have enough privileges to use /clean, I've tried it some time ago on a different backport.

[phohensee]

/sponsor

[openjdk]

Going to push as commit 728dc4d.
Since your change was applied there has been 1 commit pushed to the master branch:

• 1c13d7e: 8290839: jdk/jfr/event/compiler/TestJitRestart.java failed with "RuntimeException: No JIT restart event found: expected true, was false"

Your commit was automatically rebased without conflicts.

[openjdk]

@phohensee @Rudometov Pushed as commit 728dc4d.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.