Hi,
While running your changed tests, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check?
Full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=78587
Your paranoid android.
=== w2008s64 (32 bit report) ===
user32: input.c:1694: Test failed: expected GetMouseMovePointsEx to succeed, got 64 input.c:1702: Test failed: expected [0].x = 130, got 64 input.c:1705: Test failed: expected [0].y = 65, got 32
=== w8 (32 bit report) ===
user32: input.c:1694: Test failed: expected GetMouseMovePointsEx to succeed, got 64 input.c:1702: Test failed: expected [0].x = 130, got 64 input.c:1705: Test failed: expected [0].y = 65, got 32
=== w10pro64_2scr (32 bit report) ===
user32: input.c:3215: Test failed: expected WM_NCHITTEST message input.c:3216: Test failed: expected WM_RBUTTONDOWN message input.c:3217: Test failed: expected WM_RBUTTONUP message input.c:3246: Test failed: expected WM_LBUTTONDOWN message input.c:3247: Test failed: expected WM_LBUTTONUP message input.c:3300: Test failed: expected loop with WM_NCHITTEST messages input.c:3353: Test failed: expected WM_LBUTTONDOWN message input.c:3354: Test failed: expected WM_LBUTTONUP message
=== w10pro64_ar (32 bit report) ===
user32: input.c:1432: Test failed: Wrong new pos: (150,150)
=== w2008s64 (64 bit report) ===
user32: input.c:1694: Test failed: expected GetMouseMovePointsEx to succeed, got 64 input.c:1702: Test failed: expected [0].x = 130, got 64 input.c:1705: Test failed: expected [0].y = 65, got 32
=== w1064v1809 (64 bit report) ===
user32: input.c:1694: Test failed: expected GetMouseMovePointsEx to succeed, got 64 input.c:1702: Test failed: expected [0].x = 130, got 64 input.c:1705: Test failed: expected [0].y = 65, got 32
=== w10pro64_2scr (64 bit report) ===
user32: input.c:1694: Test failed: expected GetMouseMovePointsEx to succeed, got 64 input.c:1702: Test failed: expected [0].x = 130, got 64 input.c:1705: Test failed: expected [0].y = 65, got 32