[PATCH 1/6] user32/focus: Prevent a recursive activation loop with the activation messages

[Gabriel Ivăncescu]

Unrelated failures, the WaitForSingleObject in particular happens 
randomly on the testbot submissions.

On 12/17/18 14:02, Marvin wrote:
> 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=45743
>
> Your paranoid android.
>
>
> === debian9 (32 bit report) ===
>
> user32:
> msg.c:8713: Test failed: WaitForSingleObject failed 102
> msg.c:8719: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead
> msg.c:8719: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead
> msg.c:8719: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000
>
> === debian9 (32 bit WoW report) ===
>
> user32:
> input.c:2563: Test failed: 200: wrong deviceType 2/0
> input.c:2566: Test failed: 200: wrong originId 1/4
> input.c:2572: Test failed: 200: wrong deviceType 2/0
> input.c:2575: Test failed: 200: wrong originId 1/4
>