mirror of
https://github.com/encounter/dawn-cmake.git
synced 2025-05-30 19:21:39 +00:00
92244ec9d4
Update expectations and ts_sources
e518bfe8a4..8f2742e4a4
- 8f2742 Raise maxComputeWorkgroupStorageSize from 16352 to 16384 (#1390)
- 706082 wgsl: Add stubs for the pack and unpack methods. (#1425)
- 33d851 wgsl: Stub tests for the textureStore builtin. (#1423)
- 8610c8 wgsl: Add stub tests for textureSampleLevel. (#1422)
- 5d6c16 wgsl: Stub synchronization builtin functions. (#1426)
- c57922 Duplicate params: catch in ParamsBuilder, improve error in loadTreeForQuery (#1424)
- f923e0 Update pipeline output targets validation with different writeMask (#1174)
- 17582e wgsl: Add stub tests for textureSampleGrad. (#1421)
- dc8142 wgsl: Add stub tests for textureSampleCompareLevel. (#1420)
- fe9154 wgsl: Stub tests for textureSampleCompare (#1418)
- a0c703 wgsl: Add stubs for the read-write-modify atomic operations. (#1417)
- 2b89c0 wgsl: Add stubs for the atomicStore builtin. (#1416)
- 776015 wgsl: Stub tests for the atomicLoad builtin. (#1415)
- 544877 wgsl: Add stub tests for the textureSample builtin. (#1414)
- d6dc47 wgsl: Fixup coord parameters in texture tests. (#1410)
Created with './tools/run cts roll'
Change-Id: Ibe57ebc6643921cae7bc3fae6f82459673106dd9
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/+/90860
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Ben Clayton <bclayton@google.com>
Auto-Submit: Corentin Wallez <cwallez@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
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.