On Wed, 29 May 2024 09:56:20 GMT, Alexander Zvegintsev
wrote:
>> These changes are intended to stabilize testing on Wayland in X11
>> compatibility mode.
>>
>>
>>
>> Many tests may fail if there is no `robot.delay()` call after
>> `robot.waitForIdle()` (right after displaying a window).
>>
On Wed, 4 Sep 2024 18:50:12 GMT, Sergey Bylokhov wrote:
>> I'm not sure that this should happen, (implemenation bug?) but it is outside
>> the scope of the test updates to fix.
>
> this looks like a product bug.
see https://bugs.openjdk.org/browse/JDK-8339561
-
PR Review Comment:
On Wed, 22 May 2024 02:51:31 GMT, Alexander Zvegintsev
wrote:
>> Alexander Zvegintsev has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> spacing
>
> test/jdk/java/awt/List/KeyEventsTest/KeyEventsTest.java line 53:
>
>> 51: import jdk.test
On Wed, 29 May 2024 09:56:20 GMT, Alexander Zvegintsev
wrote:
>> These changes are intended to stabilize testing on Wayland in X11
>> compatibility mode.
>>
>>
>>
>> Many tests may fail if there is no `robot.delay()` call after
>> `robot.waitForIdle()` (right after displaying a window).
>>
On Wed, 22 May 2024 20:44:54 GMT, Phil Race wrote:
>> test/jdk/java/awt/Paint/ListRepaint.java line 40:
>>
>>> 38: static Frame frame;
>>> 39:
>>> 40: public static void main(final String[] args) throws Exception {
>>
>> It is critical to call AWT code on EDT in this test, otherwise it
> These changes are intended to stabilize testing on Wayland in X11
> compatibility mode.
>
>
>
> Many tests may fail if there is no `robot.delay()` call after
> `robot.waitForIdle()` (right after displaying a window).
>
>
> Some tests do not release previously pressed mouse button/key, this
