[PATCH] dxgi/tests: Avoid an ever chaning value in a dxgi failure message.

Francois Gouget fgouget at codeweavers.com
Mon Mar 16 05:35:35 CDT 2020

On Sun, 15 Mar 2020, Marvin wrote:
> === w2008s64 (64 bit report) ===
> dxgi:
> dxgi.c:5063: Test failed: Got unexpected message 0x46, wparam 0, lparam 0x22fa20.
> dxgi.c:5063: Test failed: Got unexpected message 0x24, wparam 0, lparam 0x22f690.
> dxgi.c:5063: Test failed: Got unexpected message 0x1a, wparam 0x2f, lparam 0x22fa48.

The patch was designed to avoid false positives from messages such as 

dxgi.c:5063: Test failed: Got unexpected message 0x31f, hwnd 001C01E4, wparam 0x1, lparam 0.

But of course it won't help with unexpected WM_WINDOWPOSCHANGING, 
WM_GETMINMAXINFO and WM_WININICHANGE messages since lparam is a pointer 
for those (lparam is sometimes NULL for WM_WININICHANGE). Fortunately 
these are pretty rare, they happened only three times in the recorded 
history (vs. 153 instances of WM_DWMNCRENDERINGCHANGED):

Jan 27 - cw-rx460-32

Jan 23 - w2008s64

Jan 01 - gtx560-32
Not available on test.winehq.org anymore.

Francois Gouget <fgouget at codeweavers.com>

More information about the wine-devel mailing list