From: Marvin Subject: Re: [PATCH v2 2/3] winex11.drv: Only send WM_CANCELMODE if a menu is active. Message-Id: Date: Wed, 13 Nov 2019 07:42:27 -0600 In-Reply-To: <20191113122807.14631-2-rbernon@codeweavers.com> References: <20191113122807.14631-2-rbernon@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=60011 Your paranoid android. === w1064v1809 (32 bit report) === user32: msg.c:10382: Test failed: did not get expected count for minimum timeout (54 != ~100). === w1064v1809_ar (32 bit report) === user32: msg.c:15592: Test failed: DefWindowProcA(SC_RESTORE):overlapped: 34: the msg sequence is not complete: expected 0000 - actual 0024 === w1064v1809_he (32 bit report) === user32: msg.c:16311: Test failed: 0: WaitForSingleObject failed === debian10 (32 bit Chinese:China report) === user32: msg.c:8809: Test failed: WaitForSingleObject failed 102 msg.c:8815: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8815: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8815: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000 === debian10 (64 bit WoW report) === user32: msg.c:8809: Test failed: WaitForSingleObject failed 102 msg.c:8815: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8815: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8815: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000