Giovanni Mascellani : tests: Mark a timestamp query test as buggy on MoltenVK.

[Alexandre Julliard]

Module: vkd3d
Branch: master
Commit: 5d4edba925537bf0b0b1dbb755439d09219306b9
URL:    https://gitlab.winehq.org/wine/vkd3d/-/commit/5d4edba925537bf0b0b1dbb755439d...

Author: Giovanni Mascellani 
Date:   Wed Dec 27 20:07:47 2023 +0100

tests: Mark a timestamp query test as buggy on MoltenVK.

The generated Vulkan calls look right and do not trigger any
validation error, but the returned timestamp is 0. A valid
timestamp is returned if the CopyResource() call is commented,
or the second EndQuery() call is moved before CopyResource(),
or the first EndQuery() call is commented. I am not seeing any
sensible pattern here, so I guess there is just a bug in
MoltenVK.

---

tests/d3d12.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/d3d12.c b/tests/d3d12.c
index fce9d05f..77579c35 100644
--- a/tests/d3d12.c
+++ b/tests/d3d12.c
@@ -24848,6 +24848,7 @@ static void test_resolve_non_issued_query_data(void)
             "Got unexpected timestamp %#"PRIx64".\n", timestamps[0]);
     ok(!timestamps[1], "Got unexpected timestamp %#"PRIx64".\n", timestamps[1]);
     ok(!timestamps[2], "Got unexpected timestamp %#"PRIx64".\n", timestamps[2]);
+    bug_if(is_mvk_device(device))
     ok(timestamps[3] != initial_data[3] && timestamps[3] > 0,
             "Got unexpected timestamp %#"PRIx64".\n", timestamps[3]);
     release_resource_readback(&rb);