[PATCH 3/3] user32/tests: Add a helper to initialize function pointers.

[Marvin]

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=96355

Your paranoid android.


=== w8 (32 bit report) ===

user32:
sysparams.c:2494: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
sysparams.c:2505: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

=== w8adm (32 bit report) ===

user32:
sysparams.c:2494: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
sysparams.c:2505: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

=== w864 (32 bit report) ===

user32:
sysparams.c:2494: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
sysparams.c:2505: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

=== w1064v1809 (32 bit report) ===

user32:
sysparams.c:2494: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
sysparams.c:2505: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

=== w1064 (32 bit report) ===

user32:
sysparams.c:2494: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
sysparams.c:2505: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

=== w1064_tsign (32 bit report) ===

user32:
sysparams.c:2494: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
sysparams.c:2505: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1

=== w10pro64 (32 bit report) ===

user32:
sysparams.c:2494: Test failed: Waiting for the WM_DISPLAYCHANGE message timed out
sysparams.c:2505: Test failed: Set bpp 32, but WM_DISPLAYCHANGE reported bpp -1