From: Marvin Subject: Re: [PATCH v2 2/6] user32/tests: Test a recursive activation loop on WM_ACTIVATE Message-Id: Date: Tue, 23 Apr 2019 10:37:21 -0500 In-Reply-To: <93a181e6693774c94b8ad0f80a64bf65c93e240b.1556030499.git.gabrielopcode@gmail.com> References: <93a181e6693774c94b8ad0f80a64bf65c93e240b.1556030499.git.gabrielopcode@gmail.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=51399 Your paranoid android. === w7pro64 (32 bit report) === user32: msg.c:13469: Test failed: 54: ShowWindow(SW_MINIMIZE): 4: in msg 0x0047 expecting wParam 0x8170 got 0x1803 msg.c:13469: Test failed: 54: ShowWindow(SW_MINIMIZE): 5: the msg 0x0003 was expected, but got msg 0x0047 instead msg.c:13469: Test failed: 54: ShowWindow(SW_MINIMIZE): 6: the msg 0x0005 was expected, but got msg 0x0003 instead msg.c:13469: Test failed: 54: ShowWindow(SW_MINIMIZE): 7: the msg sequence is not complete: expected 0000 - actual 0005 === debian9 (32 bit report) === user32: msg.c:8746: Test failed: WaitForSingleObject failed 102 msg.c:8752: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8752: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8752: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000