On Sat, 20 Dec 2025 03:31:24 GMT, Alexander Zvegintsev <[email protected]> wrote:
> This is a test stabilization changeset for intermittent failures in the CI > for Wayland. > I made minimal changes where applicable. There was no goal to refactor all > affected tests. > > * `test/jdk/java/awt/Choice/PopupPosTest/PopupPosTest.java` > Without the added delay, the `stateChanged` variable could be overwritten by > a previous `mouseMoveAndPressOnChoice` call. > * `test/jdk/java/awt/Focus/ClearLwQueueBreakTest/ClearLwQueueBreakTest.java` > The test may still fail intermittently in the CI, but an additional delay > after setVisible won't cause any problems / > https://bugs.openjdk.org/browse/JDK-8198618 > * `test/jdk/java/awt/Frame/FrameSetMinimumSizeTest.java` > The test made many setSize calls within a single `invokeAndWait` block and > immediately checked the sizes. This works on the X11 server, but the XWayland > implementation appears to be different. The `ConfigureNotify` with the > correct sizes arrives later, but the test doesn't wait for it. Therefore, it > was refactored. > * > test/jdk/java/awt/KeyboardFocusmanager/TypeAhead/ButtonActionKeyTest/ButtonActionKeyTest.java > The test may still fail intermittently in the CI, but an additional delay > after `setVisible` won't cause any problems / > https://bugs.openjdk.org/browse/JDK-8257529 > * > `test/jdk/java/awt/LightweightComponent/LightWeightTabFocus/LightWeightTabFocus.java` > mouse button was not released causing subsequent test failures. > * `test/jdk/java/awt/Modal/ToFront/DialogToFrontModeless1Test.java` > details are in the test's comment. > > This doesn't solve all the intermittent test issues related to Wayland > (sometimes not even on Wayland). > Some of the tests described in the bug report are no longer reproducible. I > will file new issues for future failures. > I also tested that it does not break other platforms testing as well. Marked as reviewed by serb (Reviewer). test/jdk/java/awt/KeyboardFocusmanager/TypeAhead/ButtonActionKeyTest/ButtonActionKeyTest.java line 92: > 90: frame.setVisible(true); > 91: Util.waitForIdle(robot); > 92: robot.delay(1000); Isn’t it suspicious that it is not possible to show the frame quickly? I mean, 1 second is quite a long time. Is there any possibility to improve this on the toolkit side? ------------- PR Review: https://git.openjdk.org/jdk/pull/28939#pullrequestreview-3601457053 PR Review Comment: https://git.openjdk.org/jdk/pull/28939#discussion_r2637532162
