From: Marvin Subject: Re: [PATCH v2] user32: Do not call SendMessage() to show a window that is already visible. Message-Id: Date: Mon, 01 Jul 2019 12:36:15 -0500 In-Reply-To: <20190701170855.439-1-alexey@prokhin.ru> References: <20190701170855.439-1-alexey@prokhin.ru> 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=54297 Your paranoid android. === w1064v1809 (32 bit report) === user32: msg.c:9314: Test failed: Shift+MouseButton press/release: 7: the msg 0x0202 was expected, but got msg 0x0007 instead msg.c:9314: Test failed: Shift+MouseButton press/release: 8: the msg 0x0202 was expected, but got msg 0x0101 instead msg.c:9314: Test failed: Shift+MouseButton press/release: 10: the msg 0x0101 should have been sent msg.c:9314: Test failed: Shift+MouseButton press/release: 11: the msg 0x0101 was expected, but got msg 0x0202 instead msg.c:9314: Test failed: Shift+MouseButton press/release: 12: the msg sequence is not complete: expected 0000 - actual 0202 === debian9 (32 bit report) === user32: msg.c:8693: Test failed: WaitForSingleObject failed 102 msg.c:8699: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8699: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8699: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000