8320057: [macos14] javax/swing/JToolTip/4846413/bug4846413.java: Tooltip has not been found!

[prsadhuk]

Test failing on macos14 citing "ToolTip not found"...Investigation shows that the mouse is not moved when invoked 1st time to desired location on screen causing tooltip to not show...However, subsequent runs of the same test without any change causes it to pass every time.
Workaround is proposed to check if running on 14.x, then invoke a dummy mouse movement to same location which causes the test to pass for several iterations in macos14 environment.

---

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-8320057: [macos14] javax/swing/JToolTip/4846413/bug4846413.java: Tooltip has not been found! (Bug - P4) ⚠️ Issue is not open.

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16776/head:pull/16776
$ git checkout pull/16776

Update a local copy of the PR:
$ git checkout pull/16776
$ git pull https://git.openjdk.org/jdk.git pull/16776/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 16776

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16776.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back psadhukhan! 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]

@prsadhuk The following label will be automatically applied to this pull request:

• client

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.

[mlbridge]

Webrevs

• 00: Full (3787fae3)

[prrace]

I don't think this is a good idea. We aren't interested in just making the test "pass".
We need to understand what changed. If necessary it could end up in a bug report to Apple.

[honkar-jdk]

Adding to Phil's point, version specific test fixes would require to be removed and/or reworked if the issue gets fixed on latest macOS update.

[victordyakov]

@prsadhuk @honkar-jdk @prrace is it ongoing next 24 hours?

[honkar-jdk]

@prsadhuk @honkar-jdk @prrace is it ongoing next 24 hours?

@victordyakov The test fix consists of macOS version specific fix - adding an extra mouse event. But since we are trying find the root cause behind the issue and it might end up being reported as Apple Bug #16776 (comment), I believe this is not being targeted for tomorrow.