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>
This commit is contained in:
Austin Eng 2022-09-13 22:16:42 +00:00 committed by Dawn LUCI CQ
parent 8a440ee3b4
commit e0cbb0cfe9
1 changed files with 1 additions and 0 deletions

View File

@ -131,6 +131,7 @@ wrapPromiseWithHeartbeat(GPUBuffer.prototype, 'mapAsync');
wrapPromiseWithHeartbeat(GPUShaderModule.prototype, 'compilationInfo'); wrapPromiseWithHeartbeat(GPUShaderModule.prototype, 'compilationInfo');
globalTestConfig.testHeartbeatCallback = sendHeartbeat; globalTestConfig.testHeartbeatCallback = sendHeartbeat;
globalTestConfig.noRaceWithRejectOnTimeout = true;
async function runCtsTest(query, use_worker) { async function runCtsTest(query, use_worker) {
const workerEnabled = use_worker; const workerEnabled = use_worker;