[PATCH 3/3] server: Create message queue and thread input in get_key_state.

[Marvin]

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

Your paranoid android.


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

user32:
input.c:2299: Test failed: Spurious WM_INPUT messages

=== w10pro64_ar (64 bit report) ===

user32:
input.c:3240: Test failed: expected WM_LBUTTONDOWN message
input.c:3241: Test failed: expected WM_LBUTTONUP message
input.c:3268: Test failed: expected WM_NCHITTEST message
input.c:3269: Test failed: expected WM_RBUTTONDOWN message
input.c:3270: Test failed: expected WM_RBUTTONUP message
input.c:3299: Test failed: expected WM_LBUTTONDOWN message
input.c:3300: Test failed: expected WM_LBUTTONUP message
input.c:3353: Test failed: expected loop with WM_NCHITTEST messages
input.c:3406: Test failed: expected WM_LBUTTONDOWN message
input.c:3407: Test failed: expected WM_LBUTTONUP message