encounter
/
dawn-cmake
mirror of https://github.com/encounter/dawn-cmake.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
dawn-cmake/webgpu-cts
History
Brian Sheedy cea7ce35be Move WebGPU worker globs 
Creates worker_test_globs.txt, which is a newline-delimited list
of globs specifying which tests should be run in workers in
addition to the usual test run. By moving the list here instead of
having it in the Chromium-side test harness, Dawn contributors can
make changes without needing a full Chromium checkout.

Chromium-side change is crrev.com/c/3739461.

Change-Id: I59e305ef24d27da7702aeed723e12b3d08847d72
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/95301
Auto-Submit: Brian Sheedy <bsheedy@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: Austin Eng <enga@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@google.com>
Reviewed-by: Austin Eng <enga@chromium.org>
 		2022-07-01 01:20:14 +00:00
..
scripts Don't use incremental build in webgpu-cts/scripts/list.py 2022-05-10 18:17:54 +00:00
webtests Add generated webtest .html files 2022-06-10 22:00:33 +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/ cef4c7678..7334f06d2 (18 commits) 2022-06-30 19:42:54 +00:00
test_page.html Change base directory for CTS runner, part 2 2022-06-24 18:50:19 +00:00
test_runner.js Report WebGPU CTS JS time 2022-06-21 20:39:14 +00:00
worker_test_globs.txt Move WebGPU worker globs 2022-07-01 01:20:14 +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.