Re: [PATCH 2/2] user32: Add SetTimer test with window procedure handle passed as timer callback

[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
https://testbot.winehq.org/JobDetails.pl?Key=21002

Your paranoid android.


=== w864 (32 bit msg) ===
msg.c:6360: Test failed: Update region shouldn't be empty
msg.c:6594: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000
msg.c:6596: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000
msg.c:6366: Test failed: Regions are different
msg.c:6366: Test failed: Regions are different
msg.c:6366: Test failed: Regions are different

=== w1064 (32 bit msg) ===
msg.c:6360: Test failed: Update region shouldn't be empty
msg.c:6594: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000
msg.c:6596: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000
msg.c:6366: Test failed: Regions are different
msg.c:6366: Test failed: Regions are different
msg.c:6366: Test failed: Regions are different

=== w1064 (64 bit msg) ===
msg.c:6360: Test failed: Update region shouldn't be empty
msg.c:6594: Test failed: InvalidateErase: 0: the msg sequence is not complete: expected 0085 - actual 0000
msg.c:6596: Test failed: Paint: 0: the msg sequence is not complete: expected 000f - actual 0000
msg.c:6366: Test failed: Regions are different
msg.c:6366: Test failed: Regions are different
msg.c:6366: Test failed: Regions are different