From: Marvin Subject: Re: [PATCH 1/6] user32: Wait for user driver to be ready in EnumDisplayDevicesW. Message-Id: Date: Thu, 04 Jul 2019 08:35:07 -0500 In-Reply-To: <4bd390ff-c388-e574-d080-83799173e019@codeweavers.com> References: <4bd390ff-c388-e574-d080-83799173e019@codeweavers.com> 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=54467 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 win.c:10127: Test failed: Expected foreground window 0, got 00E300D4 win.c:10133: Test failed: Expected foreground window 000E0120, got 00E300D4