[PATCH v3 1/4] user32/tests: Add some more tests related to the RAWINPUT structure.

[Marvin]

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=117202

Your paranoid android.


=== w7u_2qxl (32 bit report) ===

user32:
input.c:745: Test failed:  0 (a4/0): 00 from 00 -> 80 unexpected
input.c:745: Test failed:  0 (a4/0): 41 from 01 -> 00 unexpected

=== w7u_el (32 bit report) ===

user32:
input.c:4525: Test failed: SendInput triggered unexpected message 0xc042

=== w10pro64 (32 bit report) ===

user32:
input.c:4176: Test failed: 7:0: WaitForSingleObject returned 258
input.c:4119: Test failed: 7:0: expected that X highest bit is set, got 0
input.c:4120: Test failed: 7:0: expected that X keystate is set
input.c:4120: Test failed: 7:0: expected that X keystate is set
input.c:4127: Test failed: 7:0: expected that X keystate is set
input.c:4127: Test failed: 7:0: expected that X keystate is set
input.c:4119: Test failed: 7:1: expected that X highest bit is set, got 0x1
input.c:4120: Test failed: 7:1: expected that X keystate is set
input.c:4120: Test failed: 7:1: expected that X keystate is set
input.c:4127: Test failed: 7:1: expected that X keystate is set
input.c:4127: Test failed: 7:1: expected that X keystate is set
input.c:4119: Test failed: 7:2: expected that X highest bit is set, got 0
input.c:4120: Test failed: 7:2: expected that X keystate is set
input.c:4120: Test failed: 7:2: expected that X keystate is set
input.c:4127: Test failed: 7:2: expected that X keystate is set
input.c:4127: Test failed: 7:2: expected that X keystate is set
input.c:4119: Test failed: 7:3: expected that X highest bit is set, got 0x1
input.c:4120: Test failed: 7:3: expected that X keystate is set
input.c:4120: Test failed: 7:3: expected that X keystate is set
input.c:4127: Test failed: 7:3: expected that X keystate is set
input.c:4127: Test failed: 7:3: expected that X keystate is set
input.c:4119: Test failed: 8:0: expected that X highest bit is set, got 0
input.c:4120: Test failed: 8:0: expected that X keystate is set
input.c:4120: Test failed: 8:0: expected that X keystate is set
input.c:4127: Test failed: 8:0: expected that X keystate is set
input.c:4127: Test failed: 8:0: expected that X keystate is set
input.c:4119: Test failed: 8:1: expected that X highest bit is set, got 0x1
input.c:4120: Test failed: 8:1: expected that X keystate is set
input.c:4120: Test failed: 8:1: expected that X keystate is set
input.c:4127: Test failed: 8:1: expected that X keystate is set
input.c:4127: Test failed: 8:1: expected that X keystate is set
input.c:4119: Test failed: 8:2: expected that X highest bit is set, got 0
input.c:4120: Test failed: 8:2: expected that X keystate is set
input.c:4120: Test failed: 8:2: expected that X keystate is set
input.c:4127: Test failed: 8:2: expected that X keystate is set
input.c:4127: Test failed: 8:2: expected that X keystate is set
input.c:4119: Test failed: 8:3: expected that X highest bit is set, got 0x1
input.c:4120: Test failed: 8:3: expected that X keystate is set
input.c:4120: Test failed: 8:3: expected that X keystate is set
input.c:4127: Test failed: 8:3: expected that X keystate is set
input.c:4127: Test failed: 8:3: expected that X keystate is set

=== w1064_tsign (64 bit report) ===

user32:
input.c:1291: Test failed: Wrong set pos: (100,100)
input.c:1311: Test failed: GetCursorPos: (100,100)