encounter
/
dawn-cmake
mirror of https://github.com/encounter/dawn-cmake.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
dawn-cmake/webgpu-cts
History
Ben Clayton e119ff452a Roll third_party/webgpu-cts/ 900765392..21af43c62 (10 commits) 
Update expectations and ts_sources

9007653926..21af43c62a
 - 21af43 wgsl: Implement f32 `exp` test (#1315)
 - 0f86e0 Remove redundant information from unittest names (#1317)
 - 23dab0 wgsl: Stub acosh builtin tests. (#1312)
 - 7cea4a wgsl: stub distance builtin tests (#1311)
 - 8829c3 wgsl: stub length builtin tests (#1310)
 - 7eec30 wgsl: stub tests for atanh builtin. (#1314)
 - e442a7 wgsl: Stub asinh builtin tests (#1313)
 - 969db1 Implement OneULP and related ULP functions (#1218)
 - 7845e2 wgsl: Stub asin builtin tests (#1309)
 - 8f8ab3 Sync reserved words to spec. (#1308)

Created with './tools/run cts roll'

Change-Id: I6f549884d045b80b63a826a4282faa26aa992ec4
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/88260
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Auto-Submit: Ben Clayton <bclayton@google.com>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
 		2022-04-28 13:32:23 +00:00
..
scripts Fix inclusive language presubmit 2022-04-19 22:25:45 +00:00
BUILD.gn Add CTS telemetry harness support 2022-03-24 00:21:55 +00:00
README.md Add CTS telemetry harness support 2022-03-24 00:21:55 +00:00
expectations.txt Roll third_party/webgpu-cts/ 900765392..21af43c62 (10 commits) 2022-04-28 13:32:23 +00:00
test_page.html Add CTS telemetry harness support 2022-03-24 00:21:55 +00:00
test_runner.js Split large CTS logs 2022-04-14 17:19:11 +00:00

README.md

Running the WebGPU CTS Locally with Chrome

Running the WebGPU CTS locally with Chrome requires a Chromium checkout.

Follow these instructions for checking out and building Chrome. You'll also need to build the telemetry_gpu_integration_test target.

At the root of a Chromium checkout, run: ./content/test/gpu/run_gpu_integration_test.py webgpu_cts --browser=exact --browser-executable=path/to/your/chrome-executable

If you don't want to build Chrome, you can still run the CTS, by passing the path to an existing Chrome executable to the --browser-executable argument. You should still build the telemetry_gpu_integration_test target to support all harness functionality.

Useful command-line arguments:

  • -l: List all tests that would be run.
  • --test-filter: Filter tests. Run --help for more information.
  • --help: See more options.
  • --passthrough --show-stdout: Show browser output. See also --browser-logging-verbosity.
  • --extra-browser-args: Pass extra args to the browser executable.
  • --is-backend-validation: Enable backend validation. TODO: rename this to --backend-validation.