BackendVk: Remove VVL suppressions for a fixed VVL issue.
Fixed: dawn:1627 Change-Id: I7949c0604b1aa5f96f22c9191413485f6226e270 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/119480 Kokoro: Kokoro <noreply+kokoro@google.com> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
This commit is contained in:
parent
ec20758675
commit
e268e5b854
|
@ -98,10 +98,6 @@ constexpr SkippedMessage kSkippedMessages[] = {
|
||||||
// http://anglebug.com/7513
|
// http://anglebug.com/7513
|
||||||
{"VUID-VkGraphicsPipelineCreateInfo-pStages-06896",
|
{"VUID-VkGraphicsPipelineCreateInfo-pStages-06896",
|
||||||
"contains fragment shader state, but stages"},
|
"contains fragment shader state, but stages"},
|
||||||
// http://crbug.com/dawn/1627
|
|
||||||
{"VUID-vkCmdBindDescriptorSets-pDescriptorSets-00358",
|
|
||||||
"is empty (has no bindings). Use VK_NULL_HANDLE to indicate this set is unused if using "
|
|
||||||
"VK_PIPELINE_LAYOUT_CREATE_INDEPENDENT_SETS_BIT_EXT"},
|
|
||||||
|
|
||||||
// A warning that's generated on valid usage of the WebGPU API where a fragment output doesn't
|
// A warning that's generated on valid usage of the WebGPU API where a fragment output doesn't
|
||||||
// have a corresponding attachment
|
// have a corresponding attachment
|
||||||
|
|
Loading…
Reference in New Issue