Re: [PATCH 2/2] dxgi: Update swapchain containing output after Alt+Enter was used to exit fullscreen.

[Zhiyi Zhang]

Please ignore this series for now. I will send a v3 to fix the test failures.

On 10/9/20 5:04 PM, 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=80137
>
> Your paranoid android.
>
> === w2008s64 (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w8 (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w8adm (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w1064v1507 (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w1064v1809 (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64 (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_2scr (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_ar (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_he (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_ja (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_zh_CN (32 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w2008s64 (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w864 (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w1064v1507 (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w1064v1809 (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64 (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_2scr (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_ar (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_he (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_ja (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === w10pro64_zh_CN (64 bit report) ===
>
> dxgi:
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
> dxgi.c:6274: Test failed: Test 4: Got unexpected fullscreen 0x1.
>
> === debiant (32 bit Chinese:China report) ===
>
> d3d8:
> device: Timeout
>
> d3d9:
> d3d9ex.c:4947: Test failed: Failed to get display mode.
> d3d9ex.c:4949: Test failed: Failed to get display mode.
> device.c:14116: Test failed: Failed to get display mode.
> device.c:14118: Test failed: Failed to get display mode.
>
> ddraw:
> d3d.c:102: Test failed: DirectDrawCreateEx returned: 80004005
> d3d.c:2070: Test failed: DirectDrawCreate failed: 80004005.
> d3d.c:812: Test failed: DirectDrawCreate returned: 80004005
> ddrawmodes.c:84: Test failed: DirectDrawCreateEx returned: 80004005
> dsurface.c:42: Test failed: DirectDrawCreateEx returned: 80004005
> refcount.c:58: Test failed: DirectDrawCreateEx returned: 80004005
> refcount.c:210: Test failed: DirectDrawCreateEx returned: 80004005
> refcount.c:341: Test failed: DirectDrawCreateEx returned: 80004005
> visual.c:100: Test failed: DirectDrawCreateEx returned: 80004005
>
> dxgi:
> dxgi.c:6961: Test failed: Failed to get display mode.
> dxgi.c:3643: Test failed: Got unexpected hr 0x887a0004.
> dxgi.c:3644: Test failed: Got unexpected iface DEADBEEF.
> dxgi.c:3647: Test failed: Failed to create factory with IID_IUnknown, hr 0x887a0004.
> dxgi.c:5083: Test failed: Failed to create DXGI factory, hr 0x887a0004.
> Unhandled exception: page fault on read access to 0xdeadbeef in 32-bit code (0x00406af2).
>
> Report validation errors:
> dxgi:dxgi crashed (c0000005)
>
> === debiant (32 bit WoW report) ===
>
> d3d9:
> device.c:14066: Test failed: Adapter 0: Expect window rect (0,0)-(1024,768), got (0,-9)-(1024,759).