Go to file
Jonas Ådahl 5054b2a99c tests: Don't rely on latency for actually showing Wayland windows
The test runner sends a "show" command to the test clients and assumes
this was enough work done by the client to enable the compositor to map
the window. Now that we wait to show a Wayland window until the first
buffer is attached (see bug 750552), we need to make sure that we attach
a buffer before assuming that we have the final stacking order.

So, to in order to continue relying on "show" to be enough to actually
show a window, let the test client wait until it has drawn the first
frame.

This makes the tests using Wayland clients test non-flaky.

https://bugzilla.gnome.org/show_bug.cgi?id=754711
2015-12-23 12:19:36 +08:00
data data: drop mutter-wayland.desktop 2015-11-09 10:25:40 -05:00
doc Remove gtk-doc 2015-07-06 00:52:18 -07:00
po Updated POTFILES.skip 2015-11-10 01:18:27 +01:00
src tests: Don't rely on latency for actually showing Wayland windows 2015-12-23 12:19:36 +08:00
tools Clean up the source tree 2014-03-18 20:37:35 -04:00
.gitignore Update .gitignore 2015-12-14 15:17:40 -08:00
autogen.sh build: Drop deprecated autogen.sh variables 2015-03-04 21:00:48 +01:00
configure.ac Bump version to 3.19.3 2015-12-17 01:21:40 +01:00
COPYING Updated obsolete FSF postal address in COPYING 2014-01-13 11:35:48 -05:00
Makefile.am Remove gtk-doc 2015-07-06 00:52:18 -07:00
mutter.doap doap: add <programming-language> 2014-07-31 17:50:28 +02:00
NEWS Bump version to 3.19.3 2015-12-17 01:21:40 +01:00