From e0cbb0cfe919e09a78d5f1bbc0d8da17b8dbb7b3 Mon Sep 17 00:00:00 2001
From: Austin Eng <enga@chromium.org>
Date: Tue, 13 Sep 2022 22:16:42 +0000
Subject: [PATCH] CTS: set noRaceWithRejectOnTimeout

Following https://github.com/gpuweb/cts/pull/1836, this will let Chrome's
CTS runner bypass the builtin CTS timeouts in favor of our own harness
timeouts.

Bug: chromium:1340602
Change-Id: I09f25de26f28f4595c6d277050f2a71969566fdb
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/102200
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: Austin Eng <enga@chromium.org>
---
 webgpu-cts/test_runner.js | 1 +
 1 file changed, 1 insertion(+)

diff --git a/webgpu-cts/test_runner.js b/webgpu-cts/test_runner.js
index ed9e06ad5f..ff4645c905 100644
--- a/webgpu-cts/test_runner.js
+++ b/webgpu-cts/test_runner.js
@@ -131,6 +131,7 @@ wrapPromiseWithHeartbeat(GPUBuffer.prototype, 'mapAsync');
 wrapPromiseWithHeartbeat(GPUShaderModule.prototype, 'compilationInfo');
 
 globalTestConfig.testHeartbeatCallback = sendHeartbeat;
+globalTestConfig.noRaceWithRejectOnTimeout = true;
 
 async function runCtsTest(query, use_worker) {
   const workerEnabled = use_worker;