[PATCH v2 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.

1 TestBot errors prevented a full analysis of your patch.
If the test caused the operating system (e.g. Windows) to crash or
reboot you will probably have to modify it to avoid that.
Other issues should be reported to the TestBot administrators.

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

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

=== w1064v1809 (64 bit report) ===

user32:
input.c:1421: Test failed: Wrong new pos: (150,150)

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

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

=== w10pro64 (testbot log) ===

WineRunTask.pl:error: BotError: The test VM is powered off! Did the test shut it down?