Re: [PATCH] d3d11: OMSetBlendState blend states is optional
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=18332 Your paranoid android. === wvistau64 (32 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w2008s64 (32 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w7u (32 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w7pro64 (32 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w8 (32 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w864 (32 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w1064 (32 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === wvistau64 (64 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w2008s64 (64 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w7pro64 (64 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w864 (64 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f. === w1064 (64 bit d3d11) === d3d11.c:2788: Test failed: Got unexpected color 0x6400708f.
participants (1)
-
Marvin