-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8348675: TrayIcon tests fail in Ubuntu 24.10 Wayland #23329
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 azvegint! A progress list of the required criteria for merging this PR into |
|
@azvegint 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 80 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 |
| }); | ||
|
|
||
| robot.mouseMove(0, 0); | ||
| robot.mouseMove(100, 0); |
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.
I moved it away from the top left corner, because it can trigger a hot corner in Gnome(X11 session), so the following tests may fail.
Webrevs
|
|
Mailing list message from Davide Perini on client-libs-dev: I don't know what kind of tests you are running but TrayIcon is broken No one is still using xembed for trayicon, Ubuntu has some sort of On Windows does not work better: TrayIcon is rotting in the current state, it uses 20+ years old APIs, Davide On 28/01/2025 12:36, Alexander Zvegintsev wrote: |
| } else if (!SystemTray.isSupported()) { | ||
| throw new SkippedException("SystemTray is not supported on this platform."); | ||
| } else { | ||
| if (System.getProperty("os.name").toLowerCase().startsWith("win")) { |
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.
Platform.isWindows() could work better… as well Platform.isOSX() for Mac.
The case SystemTrayIconHelper.isOel7orLater() should probably also throw SkippedException.
test/jdk/java/awt/TrayIcon/TrayIconPopup/TrayIconPopupClickTest.java
Outdated
Show resolved
Hide resolved
test/jdk/java/awt/TrayIcon/TrayIconPopup/TrayIconPopupTest.java
Outdated
Show resolved
Hide resolved
| "in Windows 7/10, which is behavior by default.\n" + | ||
| "Set \"Right mouse click\" -> \"Customize notification icons\" -> " + | ||
| "\"Always show all icons and notifications on the taskbar\" true " + | ||
| "to avoid this problem. Or change behavior only for Java SE " + | ||
| "tray icon."); |
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.
These instructions are outdated, at the same time, they're visible only on the test log… I'd rather leave them as is — it's out of scope to amend the instructions to be accurate for Windows 10 and 11.
DamonGuy
left a comment
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.
I noticed the same issue when testing on Wayland for some tests regarding SystemTray/TrayIcon. One of the ones I looked at was actually TrayIconPopupTest, which you covered here. Makes sense to just skip them for now where possible.
|
/integrate |
|
Going to push as commit 6f4fc82.
Your commit was automatically rebased without conflicts. |
Several TrayIcon tests are trying to click on the system tray icon with Robot using XTest API.
Basically we have the same kind of failures as before, e.g. JDK-8280990
I also tested the same tests by clicking manually instead of using the robot, and it works as expected.
So for now, skip those tests on Wayland (and do some minor cleanup).
Testing after modifications is also green.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23329/head:pull/23329$ git checkout pull/23329Update a local copy of the PR:
$ git checkout pull/23329$ git pull https://git.openjdk.org/jdk.git pull/23329/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23329View PR using the GUI difftool:
$ git pr show -t 23329Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23329.diff
Using Webrev
Link to Webrev Comment