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=22096
Your paranoid android.
=== wvistau64 (32 bit device) === device: unhandled exception c0000005 at 740CCE1D
=== w2008s64 (32 bit device) === device: unhandled exception c0000005 at 7397CE1D
=== wvistau64 (64 bit device) === device: unhandled exception c0000005 at 0000000074AB253F
=== w2008s64 (64 bit device) === device: unhandled exception c0000005 at 0000000073DB253F
On 12 April 2016 at 10:10, Marvin testbot@winehq.org wrote:
=== wvistau64 (32 bit device) === device: unhandled exception c0000005 at 740CCE1D
So it looks like NULL is a valid input for d3d10 if the d3d11 interface is available.