Huw Davies huw@codeweavers.com writes:
On Tue, Dec 07, 2021 at 10:01:12AM -0600, Marvin wrote:
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=103547
Your paranoid android.
=== debiant2 (32 bit Chinese:China report) ===
dxgi: dxgi.c:2614: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1024,768). dxgi.c:2618: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1024,768). dxgi.c:2687: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1024,768). dxgi.c:2694: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1024,768). dxgi.c:2687: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1024,768). dxgi.c:2694: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1024,768). dxgi.c:2709: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1024,768). dxgi.c:2874: Test failed: Got monitor rect (0,0)-(800,600), expected (0,0)-(1024,768).
These look new, right?
They happen occasionally, so it's not caused by this specific patch. It may be caused by the win32u changes in general though, possibly because of timings differences. At least I don't remember seeing these before the win32u migration started.