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
Ben Clayton f122fd52a8 Roll third_party/webgpu-cts/ 72e3a2249..e88fcf99d (3 commits) 
Update:
 - expectations.txt
 - ts_sources.txt
 - resource_files.txt
 - webtest .html files


72e3a22491..e88fcf99da
 - e88fcf Implement val:queue,writeTexture:sample_count (#1703)
 - 75268b Implement val:queue,writeTexture:texture_state (#1702)
 - c4eb1d Fix testing of the offset in image_copy,layout_related:required_bytes_in_copy (#1704)

Created with './tools/run cts roll'

Change-Id: Ic1986bfac317aabfb623213bbc84dc3c38cd9a2a
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/+/97001
Commit-Queue: Ben Clayton <bclayton@google.com>
Reviewed-by: Austin Eng <enga@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
 		2022-07-23 00:21:26 +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/ 72e3a2249..e88fcf99d (3 commits) 2022-07-23 00:21:26 +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.