From: Marvin Subject: Re: [PATCH 1/2] user32: Test Get/SetWindowPlacement with invalid length. Message-Id: Date: Wed, 26 Jan 2022 15:19:02 -0600 In-Reply-To: <20220126205735.394331-1-esme@codeweavers.com> References: <20220126205735.394331-1-esme@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=106113 Your paranoid android. === w10pro64 (32 bit report) === user32: win.c:2392: Test failed: style 0x200000: expected !100 win.c:2392: Test failed: style 0x300000: expected !100 === w10pro64 (64 bit report) === user32: win.c:2392: Test failed: style 0x200000: expected !100 win.c:2392: Test failed: style 0x300000: expected !100 === debian11 (32 bit Hindi:India report) === user32: win.c:11348: Test succeeded inside todo block: child should be topmost win.c:11351: Test failed: grandchild should be topmost win.c:11359: Test failed: child should NOT be topmost win.c:11362: Test succeeded inside todo block: grandchild should NOT be topmost win.c:11365: Test failed: 012A00B4: expected NOT topmost win.c:11184: Test succeeded inside todo block: 5: hwnd 009C00B6 is still topmost