[PATCH v2 2/2] wined3d: Use valid adapter LUIDs if they are available.

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

Your paranoid android.


=== w1064v1809_2scr (32 bit report) ===

dxgi:
dxgi.c:5848: Test failed: Test 4: Got exstyle 0x108, expected 0x100.
dxgi.c:5864: Test failed: Test 4: Got exstyle 0x108, expected 0x100.
dxgi.c:5893: Test failed: Test 4: Got exstyle 0x108, expected 0x100.
dxgi.c:5922: Test failed: Test 4: Got exstyle 0x108, expected 0x100.
dxgi.c:5939: Test failed: Test 4: Got exstyle 0x108, expected 0x100.
dxgi.c:3210: Test failed: Adapter 0 output 0 test 4: CreateSwapChain failed, hr 0x8007000e.

=== debiant (32 bit report) ===

dxgi:
dxgi: Timeout

=== debiant (32 bit French report) ===

dxgi:
dxgi: Timeout

=== debiant (build log) ===

0024:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0024:err:winediag:nodrv_CreateWindow The explorer process failed to start.
Task: WineTest did not produce the win32_ja_JP report

=== debiant (32 bit WoW report) ===

dxgi:
dxgi: Timeout

=== debiant (64 bit WoW report) ===

dxgi:
dxgi: Timeout