From: Marvin Subject: Re: [PATCH 5/8] advapi32: Fix some spec file entries Message-Id: Date: Sun, 19 Jan 2020 17:05:20 -0600 In-Reply-To: <55a9de04-51f9-978b-a141-065301198a15@dawncrow.de> References: <55a9de04-51f9-978b-a141-065301198a15@dawncrow.de> 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=63387 Your paranoid android. === debian10 (32 bit WoW report) === user32: msg.c:8772: Test failed: WaitForSingleObject failed 102 msg.c:8778: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8778: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8778: 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:8772: Test failed: WaitForSingleObject failed 102 msg.c:8778: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8778: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8778: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000