vulkan: suppress Nvidia (correctly) reported error on ShieldTV
This is part of the errors in the Vulkan importing path that will be
fixed when we use SharedTextureMemory in Chromium, so just suppress it
for now.
Bug: chromium:324282958
Change-Id: Ia98a558e8e3a41fde63cd2ecc5098a42e2c3bd49
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/174020
Commit-Queue: Ben Clayton <bclayton@google.com>
Auto-Submit: Corentin Wallez <cwallez@chromium.org>
Kokoro: Ben Clayton <bclayton@google.com>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Ben Clayton <bclayton@google.com>
diff --git a/src/dawn/native/vulkan/BackendVk.cpp b/src/dawn/native/vulkan/BackendVk.cpp
index fbc0b2f..fabed04 100644
--- a/src/dawn/native/vulkan/BackendVk.cpp
+++ b/src/dawn/native/vulkan/BackendVk.cpp
@@ -146,6 +146,8 @@
{"UNASSIGNED-CoreValidation-Shader-OutputNotConsumed",
"fragment shader writes to output location 0 with no matching attachment"},
+ // There are various VVL (and other) errors in dawn::native::vulkan::ExternalImage*. Suppress
+ // them for now as everything *should* be fixed by using SharedTextureMemory in the future.
// http://crbug.com/1499919
{"VUID-VkMemoryAllocateInfo-allocationSize-01742",
"vkAllocateMemory(): pAllocateInfo->allocationSize allocationSize (4096) "
@@ -158,6 +160,8 @@
"does not match pAllocateInfo->pNext<VkImportMemoryFdInfoKHR>"},
{"VUID-VkMemoryDedicatedAllocateInfo-image-01878",
"vkAllocateMemory(): pAllocateInfo->pNext<VkMemoryDedicatedAllocateInfo>"},
+ // crbug.com/324282958
+ {"NVIDIA", "vkBindImageMemory: memoryTypeIndex"},
};
namespace dawn::native::vulkan {
