[PATCH 2/3] user32/tests: Add tests for GetKeyState / GetKeyboardState interactions.

[Rémi Bernon]

On 2/8/21 8:57 PM, Marvin wrote:
> 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=85265
> 
> Your paranoid android.
> 
> 
> === w10pro64_ja (64 bit report) ===
> 
> user32:
> input.c:3876: Test failed: 0: expected that highest bit is unset, got 0xffffff81
> input.c:3876: Test failed: 2: expected that highest bit is unset, got 0xffffff81
> input.c:2747: Test failed: 0: expected WM_MOUSEMOVE message
> input.c:2747: Test failed: 1: expected WM_MOUSEMOVE message
> input.c:2747: Test failed: 2: expected WM_MOUSEMOVE message
> 
> === w10pro64_zh_CN (64 bit report) ===
> 
> user32:
> input.c:3876: Test failed: 0: expected that highest bit is unset, got 0xffffff81
> input.c:3876: Test failed: 2: expected that highest bit is unset, got 0xffffff81
> 

I think I also messed up the todo_wine in this patch, I guess it's going 
to need another version.
-- 
Rémi Bernon <rbernon at codeweavers.com>