Skip create render pipeline deprecation warning expectation in UnsafeAPIValidationTests
The CL that fixed deprecation warning expectations landed at the same time as the CL which added this expectation and broke CQ. We shouldn't check deprecation warnings here now because the warnings for CreateRenderPipeline are temporarily disabled. Bug: none Change-Id: I99a8b6643e64f87b2354058dbac9a236c51a2afd Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/45180 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Brandon Jones <bajones@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
This commit is contained in:
parent
3fe857a621
commit
27c4f03de1
|
@ -249,7 +249,9 @@ TEST_F(UnsafeAPIValidationTest, CreateRenderPipelineAsyncDisallowed) {
|
|||
desc.cColorStates[0].format = wgpu::TextureFormat::RGBA8Unorm;
|
||||
|
||||
// Control case: CreateRenderPipeline is allowed.
|
||||
EXPECT_DEPRECATION_WARNING(device.CreateRenderPipeline(&desc));
|
||||
device.CreateRenderPipeline(&desc);
|
||||
// TODO(bajones): Enable this when the deprecation warning is re-enabled in Device.cpp.
|
||||
// EXPECT_DEPRECATION_WARNING(device.CreateRenderPipeline(&desc));
|
||||
|
||||
testing::MockCallback<WGPUCreateRenderPipelineAsyncCallback> callback;
|
||||
EXPECT_CALL(callback,
|
||||
|
|
Loading…
Reference in New Issue