Re: [v3 2/2] user32/tests: Add test for GetWindowDisplayAffinity.

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

Your paranoid android.

=== w7u (32 bit win) ===
win.c:9860: Test failed: SetWindowDisplayAffinity returned with 8
win.c:9864: Test failed: GetWindowDisplayAffinity returned unexpected affinity 0
win.c:9867: Test failed: SetWindowDisplayAffinity returned with 8

=== w7pro64 (32 bit win) ===
win.c:9860: Test failed: SetWindowDisplayAffinity returned with 8
win.c:9864: Test failed: GetWindowDisplayAffinity returned unexpected affinity 0
win.c:9867: Test failed: SetWindowDisplayAffinity returned with 8

=== w7pro64 (64 bit win) ===
win.c:9860: Test failed: SetWindowDisplayAffinity returned with 8
win.c:9864: Test failed: GetWindowDisplayAffinity returned unexpected affinity 0
win.c:9867: Test failed: SetWindowDisplayAffinity returned with 8

[v3 2/2] user32/tests: Add test for GetWindowDisplayAffinity.

[Andrew Wesie]

On Mon, Jun 26, 2017 at 3:31 PM, Marvin  wrote:
> === w7u (32 bit win) ===
> win.c:9860: Test failed: SetWindowDisplayAffinity returned with 8
> win.c:9864: Test failed: GetWindowDisplayAffinity returned unexpected
> affinity 0
> win.c:9867: Test failed: SetWindowDisplayAffinity returned with 8

The testbot Windows 7 VMs have DWM composition disabled which my test case
did not properly handle. I am stealing some code from the ddraw tests to
detect if DWM is enabled, and skip some tests if it isn't.

-Andrew