[PATCH 01/12] user32/tests: Increase test_timers count tolerance on Windows.

[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=59921

Your paranoid android.


=== wvistau64 (32 bit report) ===

user32:
msg.c:16277: Test failed: 0: WaitForSingleObject failed

=== w2008s64 (32 bit report) ===

user32:
msg.c:16277: Test failed: 0: WaitForSingleObject failed
msg.c:16277: Test failed: 7: WaitForSingleObject failed

=== w2008s64 (task log) ===

Task errors:
The task timed out

=== w8adm (32 bit report) ===

user32:
msg.c:12930: Test failed: WmMouseHoverSeq: 5: the msg sequence is not complete: expected 0000 - actual 001a

=== w1064v1809_ja (32 bit report) ===

user32:
msg.c:8766: Test failed: MsgWaitForMultipleObjects failed 102

=== w1064v1809_zh_CN (32 bit report) ===

user32:
msg.c:16277: Test failed: 1: WaitForSingleObject failed

=== w864 (64 bit report) ===

user32:
msg.c:12420: Test failed: expected PeekMessage to return FALSE, got 1

=== debian10 (32 bit Japanese:Japan report) ===

user32:
msg.c:8774: Test failed: WaitForSingleObject failed 102
msg.c:8780: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead
msg.c:8780: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead
msg.c:8780: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000