dawn-cmake/webgpu-cts
Ben Clayton 2880e7062c Roll third_party/webgpu-cts/ d275c5e1e..fee6d96eb (5 commits)
Update expectations and ts_sources

d275c5e1e3..fee6d96eb3
 - fee6d9 Roll @webgpu/types to 0.1.18 (#1506)
 - 70df7a Add api,validation,resource_usages,buffer,in_pass_encoder:* - Part V (#1496) (#1502)
 - 6302a6 Change importExternalTexture,destroy to importExternalTexture,expired (#1474)
 - f188c0 Fix unnecessary imports
 - 8afdd9 Update texture format tests to expect exceptions

Created with './tools/run cts roll'

Change-Id: I8bcbca1747f0a2f1414b883860144817a1e16a8a
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/+/92721
Auto-Submit: Ben Clayton <bclayton@google.com>
Commit-Queue: Austin Eng <enga@chromium.org>
Reviewed-by: Austin Eng <enga@chromium.org>
2022-06-07 20:26:04 +00:00
..
scripts Don't use incremental build in webgpu-cts/scripts/list.py 2022-05-10 18:17:54 +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/ d275c5e1e..fee6d96eb (5 commits) 2022-06-07 20:26:04 +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.