mirror of
https://github.com/encounter/dawn-cmake.git
synced 2025-05-15 03:41:34 +00:00
00e845cfdf
Update expectations and ts_sources
45d2ccd250..88c0348191
- 88c034 ShaderValidationTest: remove string overload (#1184)
- 93932e Split WGSL test files (#1183)
- 40b847 Minor comment fixes
- 6f46b8 Cleanup old WGSL test files. (#1181)
Created with './tools/run cts roll'
Change-Id: I35ea8385af6ddc09c43833d40395c80f7d060002
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/87703
Auto-Submit: Ben Clayton <bclayton@google.com>
Reviewed-by: Austin Eng <enga@chromium.org>
Commit-Queue: Austin Eng <enga@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
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--helpfor 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.