[Bug 52983] New: d3d8:device - test_wndproc() fails systematically on Wine

[WineHQ Bugzilla]

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

Bug ID: 52983
           Summary: d3d8:device - test_wndproc() fails systematically on
                    Wine
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: directx-d3d
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

d3d8:device - test_wndproc() fails systematically on Wine:

device.c:3212: Test failed: Expected message 0x3 for window 0, but didn't
receive it, i=49.
device.c:3359: Test failed: Expected message 0x3 for window 0x1, but didn't
receive it.

https://test.winehq.org/data/patterns.html#d3d8:device

As far as I can tell the missing "message 0x3 for window 0x1" is present every
time, while the one for "window 0" is only present most of the time but not
necessarily on the same iteration.

[Bug 52983] d3d8:device - test_wndproc() fails systematically on Wine

[WineHQ Bugzilla]

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

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
           Keywords|                            |source, testcase

[Bug 52983] d3d8:device - test_wndproc() fails systematically on Wine

[WineHQ Bugzilla]

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

--- Comment #1 from François Gouget  ---
Nowadays we also get this similar failure mode:

device.c:3203: Test failed: Expected message 0x1c for window 0x1, but didn't
receive it, i=1.
device.c:3350: Test failed: Expected message 0x3 for window 0x1, but didn't
receive it.

[Bug 52983] d3d8:device - test_wndproc() fails systematically on Wine

[WineHQ Bugzilla]

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

--- Comment #2 from François Gouget  ---
Yet another variant:

device.c:2795: Test failed: Got unexpected wparam 0 for message 0x1c, expected
0x1.
device.c:3350: Test failed: Expected message 0x3 for window 0x1, but didn't
receive it.

[Bug 52983] d3d8:device & d3d9:device - test_wndproc() fails systematically on Wine

[WineHQ Bugzilla]

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

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|d3d8:device -               |d3d8:device & d3d9:device -
                   |test_wndproc() fails        |test_wndproc() fails
                   |systematically on Wine      |systematically on Wine

--- Comment #3 from François Gouget  ---
This also impacts d3d9:device.

[Bug 52983] d3d8:device & d3d9:device - test_wndproc() fails systematically on Wine

[WineHQ Bugzilla]

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

--- Comment #4 from François Gouget  ---
Over the past 8 months the d3d8:device variant only happened from 2022-11-24 to
2022-12-15 and only on the TestBot's debian11 and debian11b VMs.
That means it disappeared for a while (at least from 2022-07-04 to 0222-11-23),
then resurfaced and now disappeared again. So it's hard to tell if it's gone
for good or not.

The d3d9:device variant started happening on 2022-11-23 and since then it is
essentially only happening on the GitLab CI:
* It happened on debian11-win32-ja-JP on 2022-12-01.
* It happened on debian11-win32-zh_CN on 2022-12-09.
* All 123 instances since 2022-11-23 have happened on gitlab-debian, as
recently as 2023-03-03.