mirror of
https://github.com/encounter/dawn-cmake.git
synced 2025-10-24 18:50:29 +00:00
9de123fc85
These tests used to be flaky, and now fail consistently after jobs is set to 1 instead of 4. Suppressing so parallelization can be disabled to make test results more consistent. Bug: chromium:1353938 Change-Id: Ia99445ddd43d55d7ac3f67dd8e177b0fd34d51f3 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/99762 Commit-Queue: Austin Eng <enga@chromium.org> Kokoro: Kokoro <noreply+kokoro@google.com> Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.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.