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
Austin Eng 84958ea2f2 Roll third_party/webgpu-cts/ 547d67bc2..249f2b79 (8 commits) 
Update expectations and ts_sources

547d67bc22..249f2b797b
 - 249f2b Don't block on subcases until the end of a testcase (#1335)
 - 170d7b Sparse color attachment fix (#1344)
 - 423df1 DevicePool: merge default holder into the DescriptorToHolderMap (#1343)
 - 10ce93 remove doInit/doFinalize (#1342)
 - d5cf9a Handle backends flushing inputs in `atan2` tests (#1340)
 - 318d3d Move test device selection to an optional before clause (#1333)
 - ece4eb Fix non-object-type test-parameter values (#1336)
 - 5906dc Add --colors flag for enabling color output (#1338)

Created with './tools/run cts roll'

Change-Id: I070d813ffe3017e1bd4e425247f1ea174ee63887
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/+/88720
Reviewed-by: Ben Clayton <bclayton@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: Austin Eng <enga@chromium.org>
 		2022-05-03 22:07:16 +00:00
..
scripts Fix inclusive language presubmit 2022-04-19 22:25:45 +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/ 547d67bc2..249f2b79 (8 commits) 2022-05-03 22:07:16 +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.