[PATCH 1/2] d3d11/tests: Run test_instanced_draw separately.
Signed-off-by: Stefan Dösinger <stefan(a)codeweavers.com> --- There are more random test failures in d3d11 and d3d10core that I am trying to isolate, including one that cases a segfault. test_stream_output_vs() is suspicious as well, we already separate it in d3d10core. --- dlls/d3d11/tests/d3d11.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/dlls/d3d11/tests/d3d11.c b/dlls/d3d11/tests/d3d11.c index b8fa462dc39..2dfb1cc0bf5 100644 --- a/dlls/d3d11/tests/d3d11.c +++ b/dlls/d3d11/tests/d3d11.c @@ -34001,7 +34001,6 @@ START_TEST(d3d11) queue_test(test_scissor); queue_test(test_clear_state); queue_test(test_il_append_aligned); - queue_test(test_instanced_draw); queue_test(test_vertex_id); queue_test(test_fragment_coords); queue_test(test_initial_texture_data); @@ -34116,4 +34115,9 @@ START_TEST(d3d11) queue_test(test_dynamic_map_synchronization); run_queued_tests(); + + /* This test fails randomly on Win10 when run together with others + * on Radeon GPUs. Radeon 560 (0x1002:0x67ef), both on the testbot + * and Stefan's macbook. */ + test_instanced_draw(); } -- 2.34.1
Signed-off-by: Stefan Dösinger <stefan(a)codeweavers.com> --- dlls/d3d10core/tests/d3d10core.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/dlls/d3d10core/tests/d3d10core.c b/dlls/d3d10core/tests/d3d10core.c index ca12f185ec5..5a7ad3fc93b 100644 --- a/dlls/d3d10core/tests/d3d10core.c +++ b/dlls/d3d10core/tests/d3d10core.c @@ -19268,7 +19268,6 @@ START_TEST(d3d10core) queue_test(test_private_data); queue_test(test_state_refcounting); queue_test(test_il_append_aligned); - queue_test(test_instanced_draw); queue_test(test_fragment_coords); queue_test(test_initial_texture_data); queue_test(test_update_subresource); @@ -19342,4 +19341,8 @@ START_TEST(d3d10core) /* There should be no reason this test can't be run in parallel with the * others, yet it fails when doing so. (AMD Radeon HD 6310, Windows 7) */ test_stream_output_vs(); + /* Same here, this test fails randomly on Win10 when run together with + * others on Radeon GPUs. Radeon 560 (0x1002:0x67ef), both on the testbot + * and Stefan's macbook. */ + test_instanced_draw; } -- 2.34.1
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=105151 Your paranoid android. === w1064v1809 (32 bit report) === d3d11: d3d11.c:5924: Test failed: Got unexpected IAVertices count: 0. d3d11.c:5925: Test failed: Got unexpected IAPrimitives count: 0. d3d11.c:5926: Test failed: Got unexpected VSInvocations count: 0. d3d11.c:5929: Test failed: Got unexpected CInvocations count: 0. d3d11.c:5930: Test failed: Got unexpected CPrimitives count: 0. === w10pro64 (32 bit report) === d3d11: d3d11.c:5769: Test failed: Got unexpected query result 0x0000000000000000. d3d11.c:5924: Test failed: Got unexpected IAVertices count: 0. d3d11.c:5925: Test failed: Got unexpected IAPrimitives count: 0. d3d11.c:5926: Test failed: Got unexpected VSInvocations count: 0. d3d11.c:5929: Test failed: Got unexpected CInvocations count: 0. d3d11.c:5930: Test failed: Got unexpected CPrimitives count: 0. === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:28259: Test failed: d3d11.c:28259: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. === debian11 (64 bit WoW report) === d3d11: d3d11.c:28259: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28268: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.
participants (3)
-
Henri Verbeet -
Marvin -
Stefan Dösinger