[Bug 55768] New: gdi32:driver - test_D3DKMTCheckOcclusion() sometimes gets unexpected success on Windows

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55768

Bug ID: 55768
           Summary: gdi32:driver - test_D3DKMTCheckOcclusion() sometimes
                    gets unexpected success on Windows
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdi32
          Assignee: [e-mail]
          Reporter: [e-mail]

gdi32:driver - test_D3DKMTCheckOcclusion() sometimes gets unexpected success on
Windows:

driver.c:770: Test failed: Got unexpected return code 0.
driver.c:784: Test failed: Got unexpected return code 0.
driver.c:789: Test failed: Got unexpected return code 0.

See https://test.winehq.org/data/patterns.html#gdi32:driver

Where 0 == STATUS_SUCCESS

The test expects success in dual screen configurations and
STATUS_GRAPHICS_PRESENT_OCCLUDED otherwise. The failures all happen when a
single-screen configuration gets success instead of the expected occlusion
error.
That's quite rare and happens irregularly though:

* 2023-02-23 win22H2_fgtb-w10pro64-rx550-64
* 2023-03-02 win1507_newtb-w1064v1507-32
* 2023-03-09 win81_newtb-w864-64
* 2023-03-29 win1507_newtb-w1064v1507-32
* 2023-04-18 win1507_newtb-w1064v1507-32
* 2023-09-08 win1507_newtb-w1064v1507-64
* 2023-10-09 win1507_newtb-w1064v1507-64

Maybe it's caused by interference from another test?