Hi,
It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated.
The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details:
The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=125459
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
user32: input.c:746: Test failed: 0 (a4/0): 00 from 00 -> 80 unexpected input.c:746: Test failed: 0 (a4/0): 41 from 01 -> 00 unexpected
=== w7u_el (32 bit report) ===
user32: input.c:4551: Test failed: SendInput triggered unexpected message 0xc042 input.c:2404: Test failed: Spurious WM_INPUT messages
=== w10pro64 (32 bit report) ===
user32: menu.c:3368: Test failed: TrackPopupMenu returned 1 expected zero
=== w10pro64_en_AE_u8 (64 bit report) ===
user32: msg.c:13444: Test failed: coords not changed: (101 101) (101 101) msg.c:13462: Test failed: coords not changed: (101 101) (101 101)
=== w10pro64_ar (64 bit report) ===
user32: msg.c:13444: Test failed: coords not changed: (101 101) (101 101) msg.c:13462: Test failed: coords not changed: (101 101) (101 101)
=== w10pro64_ja (64 bit report) ===
user32: msg.c:7579: Test failed: down to radio3: 10: the msg sequence is not complete: expected 0000 - actual 0084
=== w10pro64_ar (64 bit report) ===
user32: win.c:4558: Test failed: hwnd 0000000000B9031C/0000000000B9031C message 0200 win.c:4563: Test failed: hwnd 0000000000B9031C/0000000000B9031C message 0203 win.c:4567: Test failed: message 0202 available