mirror of
https://github.com/encounter/dawn-cmake.git
synced 2025-06-17 12:03:43 +00:00
afbc260f14
Update expectations and ts_sources
8f2742e4a4..e48651de01
- e48651 Draw vertex buffer access test for vertex step mode buffer (#1450)
- 0dd740 sort and comment
- 36b070 part 4: no-floating-promises
- bd4473 part 3: no-unnecessary-type-assertion
- 31154b part 2: unbound-method
- 05a264 Add "recommended" typescript-eslint lints (part 1)
Created with './tools/run cts roll'
Change-Id: If45ec0f188f2b875bd6a839a3385403ddc33dcf4
Cq-Include-Trybots: luci.chromium.try:dawn-try-win10-x86-rel,linux-dawn-rel,mac-dawn-rel,win-dawn-rel
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/90802
Auto-Submit: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@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.