[PATCH 1/6] user32: Check invalid device names in EnumDisplaySettingsExW().

Zhiyi Zhang zzhang at codeweavers.com
Fri Jul 24 08:01:15 CDT 2020



On 7/24/20 6:19 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=76041
>
> Your paranoid android.
>
>
> === w8 (32 bit report) ===
>
> user32:
> sysparams.c:2508: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2519: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === w8adm (32 bit report) ===
>
> user32:
> sysparams.c:2508: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2519: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === w1064v1809 (32 bit report) ===
>
> user32:
> sysparams.c:2508: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2519: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === w1064v1809_2scr (32 bit report) ===
>
> user32:
> sysparams.c:2508: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2519: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === w1064v1809_ar (32 bit report) ===
>
> user32:
> sysparams.c:2508: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2519: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === w1064v1809_he (32 bit report) ===
>
> user32:
> sysparams.c:2508: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2519: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === w1064v1809_ja (32 bit report) ===
>
> user32:
> sysparams.c:2508: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2519: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === w1064v1809_zh_CN (32 bit report) ===
>
> user32:
> sysparams.c:2508: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2519: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === debiant (32 bit report) ===
>
> user32:
> monitor: Timeout
> msg: Timeout
> resource: Timeout
> scroll: Timeout
> static: Timeout
> sysparams: Timeout
>
> === debiant (build log) ===
>
> The task timed out
>
> === debiant (32 bit WoW report) ===
>
> user32:
> monitor: Timeout
> msg: Timeout
> resource: Timeout
> scroll: Timeout
> static: Timeout
>
> === debiant (build log) ===
>
> The task timed out
Looks like that mysterious monitor timeout bug again, but this time it's nondeterministic.
For example, a successful run is in https://testbot.winehq.org/JobDetails.pl?Key=76035





More information about the wine-devel mailing list