From 8cf61c859ddef8b088d10c31c08940a5aecda1fe Mon Sep 17 00:00:00 2001 From: Giovanni Mascellani Date: Thu, 13 Mar 2025 22:41:41 +0100 Subject: [PATCH] tests: Mark a few other timestamp query tests as buggy on MoltenVK. Similarly to 5d4edba925537bf0b0b1dbb755439d09219306b9, it seems that sometimes MoltenVK returns 0 to timestamp queries. It doesn't happen deterministically and it might depend on the hardware (I have seen differences between the M2 I used some time ago and the M3 Max I have now). --- tests/d3d12.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tests/d3d12.c b/tests/d3d12.c index e7c77bbe..6a7879a5 100644 --- a/tests/d3d12.c +++ b/tests/d3d12.c @@ -24919,6 +24919,7 @@ static void test_query_timestamp(void) for (i = 0; i < ARRAY_SIZE(timestamps) - 1; ++i) { + bug_if(is_mvk_device(device)) ok(timestamps[i] <= timestamps[i + 1], "Expected timestamps to monotonically increase, " "but got %"PRIu64" > %"PRIu64".\n", timestamps[i], timestamps[i + 1]); } @@ -24926,6 +24927,7 @@ static void test_query_timestamp(void) time_diff = (uint64_t)difftime(time_end, time_start) * timestamp_frequency; timestamp_diff = timestamps[ARRAY_SIZE(timestamps) - 1] - timestamps[0]; + bug_if(is_mvk_device(device)) ok(timestamp_diff <= time_diff, "Expected timestamp difference to be bounded by CPU time difference, " "but got %"PRIu64" > %"PRIu64".\n", timestamp_diff, time_diff); @@ -25243,6 +25245,7 @@ static void test_resolve_non_issued_query_data(void) get_buffer_readback_with_command_list(readback_buffer, DXGI_FORMAT_UNKNOWN, &rb, queue, command_list); timestamps = get_readback_data(&rb.rb, 0, 0, 0, sizeof(*timestamps)); + bug_if(is_mvk_device(device)) ok(timestamps[0] != initial_data[0] && timestamps[0] > 0, "Got unexpected timestamp %#"PRIx64".\n", timestamps[0]); ok(!timestamps[1], "Got unexpected timestamp %#"PRIx64".\n", timestamps[1]);