Re: [PATCH 5/5] user32/tests: Try to read the dpi from the user key first

[Marvin]

Hi,

While running your changed tests on Windows, 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=30508

Your paranoid android.


=== w8 (32 bit sysparams) ===
sysparams.c:2517: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
sysparams.c:2528: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

=== w1064 (32 bit sysparams) ===
sysparams.c:204: Test failed: Unexpected WM_DISPLAYCHANGE message

[PATCH 5/5] user32/tests: Try to read the dpi from the user key first

[Huw Davies]

On Thu, Apr 27, 2017 at 05:17:52AM -0500, Marvin wrote:
> Hi,
>
> While running your changed tests on Windows, 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=30508
>
> Your paranoid android.
>
> === w8 (32 bit sysparams) ===
> sysparams.c:2517: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2528: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === w1064 (32 bit sysparams) ===
> sysparams.c:204: Test failed: Unexpected WM_DISPLAYCHANGE message

These are failures not related to this patch.

Huw.