Apparently this test is flaky, based on the output I recieved we had
processed the un-fullscreen but not the un-maximise.
It seems possible the wayland thread could process when there's only one
request in the queue.
graesslin |
KWin |
Apparently this test is flaky, based on the output I recieved we had
processed the un-fullscreen but not the un-maximise.
It seems possible the wayland thread could process when there's only one
request in the queue.
Couldn't reproduce the original issue, it's a blind patch but the
current tests still pass.
Automatic diff as part of commit; lint not applicable. |
Automatic diff as part of commit; unit tests not applicable. |
I'll add the patch to my build and try to reproduce. I got the problem about every third run, so if it runs 10 times without failure I'll call it success
xvfb-run ctest --output-on-failure --repeat-until-fail 10 -I 52,52 Test project /home/martin/build/kde/workspace/kwin Start 52: kwin-testShellClient Test #52: kwin-testShellClient ............. Passed 29.80 sec Start 52: kwin-testShellClient Test #52: kwin-testShellClient ............. Passed 29.90 sec Start 52: kwin-testShellClient Test #52: kwin-testShellClient ............. Passed 30.02 sec Start 52: kwin-testShellClient Test #52: kwin-testShellClient ............. Passed 29.96 sec Start 52: kwin-testShellClient Test #52: kwin-testShellClient ............. Passed 30.00 sec Start 52: kwin-testShellClient Test #52: kwin-testShellClient ............. Passed 30.00 sec Start 52: kwin-testShellClient Test #52: kwin-testShellClient ............. Passed 30.01 sec Start 52: kwin-testShellClient Test #52: kwin-testShellClient ............. Passed 29.99 sec Start 52: kwin-testShellClient Test #52: kwin-testShellClient ............. Passed 29.99 sec Start 52: kwin-testShellClient 1/1 Test #52: kwin-testShellClient ............. Passed 30.02 sec 100% tests passed, 0 tests failed out of 1 Total Test time (real) = 299.72 sec