Re: [PATCH 5/5] user32: Implement GetRawInputDeviceInfoW completely on user side. (resend)

[Marvin]

Hi,

While running your changed tests on Windows, 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
http://testbot.winehq.org/JobDetails.pl?Key=15692

Your paranoid android.


=== WVISTAADM (32 bit input) ===
input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

=== W2K8SE (32 bit input) ===
input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

=== W7PRO (32 bit input) ===
input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

=== W7PROX64 (32 bit input) ===
input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

=== TEST64_W7SP1 (32 bit input) ===
input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

=== W7PROX64 (64 bit input) ===
input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737

=== TEST64_W7SP1 (64 bit input) ===
input.c:1787: Test failed: GetRawInputDeviceInfoA should have failed: 32, 32, -559038737