mirror of
https://github.com/encounter/dawn-cmake.git
synced 2025-07-31 01:15:56 +00:00
5f5bd214f7
Update:
- expectations.txt
- ts_sources.txt
- resource_files.txt
- webtest .html files
a41bc407a8..72e3a22491
- 72e3a2 Expand map_detach test for buffer should detach on device.destroy (#1699)
- d5e662 Enhance val:render_pass_descriptor:depth_stencil_attachment_depth_clear_value (#1674)
- 12b775 Implement val:CopyExternalImageToTexture,destination_texture,dimension (#1695)
- 2834ce Add an out-of-range check to the ranges test in writeBuffer.spec.ts (#1663)
- bee493 Implement val:queue:writeTexture:usage (#1675)
- ea0057 Add GPURenderPassDescriptor.maxDrawCount test plan (#1614)
- d30940 Generate full range of `atan2` cases (#1679)
- 5b9641 Correct the order of params in atan2 message (#1677)
- 228c28 Implement f32 `degrees` tests (#1668)
- 4786c2 Remove obsolete f32 testing infrastructure (#1665)
- 8e1167 Add f32 tests for `pow` (#1658)
- aa0719 Make `render_pass_descriptor:resolveTarget,usage` test a valid case together (#1660)
- 6dfee4 Submit all shader batches before checking for results
- bbd744 Convert `ldexp` tests to use interval framework (#1659)
- 9d3043 Update f32 tests to handle returning undefined for infinity (#1655)
Created with './tools/run cts roll'
Change-Id: Ibdf6a28ea84e2115103c9c9637b3e648a62b8364
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/+/96880
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Austin Eng <enga@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.