Skip to content
Snippets Groups Projects
Commit 5d4edba9 authored by Giovanni Mascellani's avatar Giovanni Mascellani Committed by Alexandre Julliard
Browse files

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.
parent 66cd2af1
Branches
Tags
1 merge request!545vkd3d: Assorted fixes for MoltenVK, part 2.
......@@ -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);
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment