mirror of
https://github.com/encounter/dawn-cmake.git
synced 2025-06-05 06:03:34 +00:00
c1f9e47a9b
Update:
- expectations.txt
- ts_sources.txt
- resource_files.txt
- webtest .html files
7334f06d2b..6c0f3bab40
- 6c0f3b Update the descriptions of the tests of in_pass_encoder.spec.ts (#1598)
- 7c96bd Fix an arithmitic error in memcpy
- 6121d9 Address feedback from Austin
- 145914 Optimized several expensive methods texture tests
- dd6ecd Adjust skip criteria based on suggestion from Austin
- a5c733 Guard against writeTimestamp() calls without the proper feature
- 85f975 Describe each test of the validation tests in render|compute pass encoder (#1573)
- 0bf125 Convert `min` tests to use interval framework (#1596)
- 88a46e Convert multiplication tests to use interval framework (#1591)
- 2379b9 Convert division tests to use interval framework (#1590)
- 7cdef8 Convert `max` tests to use interval framework (#1595)
Created with './tools/run cts roll'
Change-Id: Ife3d6b89275ad66887d037aa4c66b385b2e1acbc
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/+/95480
Auto-Submit: Dan Sinclair <dsinclair@chromium.org>
Commit-Queue: Dan Sinclair <dsinclair@chromium.org>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
Reviewed-by: Ryan Harrison <rharrison@chromium.org>
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.