From: Marvin Subject: Re: [PATCH 2/2] user32/listbox: Set the selection if it's currently invalid in HandleTimer Message-Id: Date: Fri, 25 Jan 2019 07:09:36 -0600 In-Reply-To: <53bb0c5421c79c5b44b5064b733a66aee61eeac2.1548416663.git.gabrielopcode@gmail.com> References: <53bb0c5421c79c5b44b5064b733a66aee61eeac2.1548416663.git.gabrielopcode@gmail.com> 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=46660 Your paranoid android. === debian9 (32 bit report) === user32: menu.c:2354: Test failed: test 27 menu: Timeout === debian9 (64 bit WoW 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