Re: [PATCH 2/4] user32/tests: Correctly restore the caption sizes when run in DPI scaling mode.

[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=30112

Your paranoid android.


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

=== w864 (32 bit sysparams) ===
sysparams.c:272: SPI_SETSCREENSAVETIMEOUT failed for reason: 329. Indicating test failure and skipping remainder of test
sysparams.c:273: Test failed: SystemParametersInfoA: rc=0 err=329
sysparams.c:273: Test failed: SystemParametersInfoA: rc=0 err=329
sysparams.c:2500: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
sysparams.c:2511: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

[PATCH 2/4] user32/tests: Correctly restore the caption sizes when run in DPI scaling mode.

[Huw Davies]

On Tue, Apr 11, 2017 at 08:17:57AM -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=30112
>
> Your paranoid android.
>
> === w8 (32 bit sysparams) ===
> sysparams.c:2500: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2511: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1
>
> === w864 (32 bit sysparams) ===
> sysparams.c:272: SPI_SETSCREENSAVETIMEOUT failed for reason: 329. Indicating test failure and skipping remainder of test
> sysparams.c:273: Test failed: SystemParametersInfoA: rc=0 err=329
> sysparams.c:273: Test failed: SystemParametersInfoA: rc=0 err=329
> sysparams.c:2500: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
> sysparams.c:2511: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

These are all unrelated.  Indeed this series is essentially a NOP for
all of the testbot VMs, since they run at 96 dpi.  Here's a real NOP,
which shows similar failures:
https://testbot.winehq.org/JobDetails.pl?Key=30122

It's interesting that when run from winetest, these tests mostly
succeed.

Huw.