This sometimes waits forever, timing out the whole test.
See for instance:
https://test.winehq.org/data/ce72f9b4263a898503c154a37df6bc9d43153f4b/win200... https://test.winehq.org/data/2a667e28ba7800288f5873a4b13bc0baf6e4a857/win200... https://test.winehq.org/data/44b30c42cbb231e3ea54a47f6ecc19e641e5f889/win200...
Signed-off-by: Rémi Bernon rbernon@codeweavers.com ---
As it's supposed to wait for the mouse to move and it then times out I don't expect the test to suddenly succeed, but at least it won't make the whole run time out.
dlls/user32/tests/msg.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/dlls/user32/tests/msg.c b/dlls/user32/tests/msg.c index 7eaa2c67945..469c193c1a3 100644 --- a/dlls/user32/tests/msg.c +++ b/dlls/user32/tests/msg.c @@ -12523,8 +12523,9 @@ done: static void wait_move_event(HWND hwnd, int x, int y) { MSG msg; - DWORD timeout = GetTickCount() + 500, delay; + DWORD timeout = GetTickCount() + 500; BOOL ret; + int delay;
while ((delay = timeout - GetTickCount()) > 0) {