[PATCH v2 1/3] user32/tests: Skip inconsistent OemKeyScan tests on non-us keyboard.
Marvin
testbot at winehq.org
Fri May 14 09:13:15 CDT 2021
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=90496
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
user32:
input.c:757: Test failed: 0 (a4/0): 00 from 00 -> 80 unexpected
input.c:757: Test failed: 0 (a4/0): 41 from 01 -> 00 unexpected
=== w1064v1809 (32 bit report) ===
user32:
input.c:2784: Test failed: 0: expected WM_MOUSEMOVE message
input.c:2784: Test failed: 1: expected WM_MOUSEMOVE message
input.c:2784: Test failed: 2: expected WM_MOUSEMOVE message
=== wvistau64 (64 bit report) ===
user32:
input.c:757: Test failed: 0 (a4/0): 01 from 01 -> 00 unexpected
input.c:757: Test failed: 0 (a4/0): 11 from 01 -> 00 unexpected
input.c:757: Test failed: 0 (a4/0): a2 from 01 -> 00 unexpected
=== w1064_2qxl (64 bit report) ===
user32:
input.c:1303: Test failed: Wrong set pos: (100,100)
input.c:1323: Test failed: GetCursorPos: (100,100)
=== w10pro64 (64 bit report) ===
user32:
input.c:1303: Test failed: Wrong set pos: (100,100)
input.c:1323: Test failed: GetCursorPos: (100,100)
More information about the wine-devel
mailing list