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=33191
Your paranoid android.
=== w8 (32 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
=== w864 (32 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
=== w1064 (32 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
=== w864 (64 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
=== w1064 (64 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
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=33190
Your paranoid android.
=== w8 (32 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
=== w864 (32 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
=== w1064 (32 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
=== w864 (64 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
=== w1064 (64 bit device) ===
device.c:6945: Test failed: Got unexpected hr 0.
On 20 September 2017 at 07:13, Alex Henrie <alexhenrie24(a)gmail.com> wrote:
> Fixes https://bugs.winehq.org/show_bug.cgi?id=37160
>
> The other option is to add D3D_DISABLE_9EX checks to d3d9.h, but I don't
> think it will break anything to declare the new stuff unconditionally.
>
I'd rather do it right.
On Tue, 2017-09-19 at 00:23 -0500, Zebediah Figura wrote:
> This effectively reverts 3c444ea350e0688247bd2056b3861dac4af08fbc,
> which should not be necessary, and in fact does not affect the
> linked application, MSN Messenger.
This needs a test.