mirror of
https://github.com/encounter/dawn-cmake.git
synced 2025-05-16 12:21:35 +00:00
e37f0a1943
There are many devices in Intel HD630 family, we cannot enumerate all their device ids in the tag. We want cts to run as expected on other Intel devices of the same architecture, add generation-based tag intel-gen-9 to include a broad range of devices in the expectations. Bug: dawn:1444 Change-Id: I80b6ae64ea2efc41bcc68e1c917919a86ec87f44 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/97760 Kokoro: Kokoro <noreply+kokoro@google.com> Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Brian Sheedy <bsheedy@google.com> Reviewed-by: Austin Eng <enga@chromium.org>
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.