mirror of https://github.com/encounter/dawn-cmake.git synced 2025-05-16 20:31:20 +00:00

History

Ben Clayton 1524d9e1bf Roll third_party/webgpu-cts/ 27dc745ca..a6451cc67 (19 commits)

Update:
 - expectations.txt
 - ts_sources.txt
 - resource_files.txt
 - webtest .html files


27dc745ca1..a6451cc673
 - a6451c Update 'buffer,usage' test in createBindGroup.spec.ts (#1824)
 - 0007e6 Add 'buffer,resource_offset' to createBindGroup.spec.ts (#1825)
 - a40f43 shader/execution: Fix shader creation errors (#1827)
 - 25c9f4 Add 'buffer,usage' test to createBindGroup.spec.ts (#1820)
 - 888ada slightly broaden/simplify pipeline_output_targets (#1823)
 - 708441 test ~all cases of pipeline_output_targets,blend (#1822)
 - 399cd2 Fix a wrong bit operation to decide the validation in indirect_dispatch_buffer,usage (#1819)
 - 73c9e8 Add storage_texture,mip_level_count test to createBindGroup.spec.ts (#1818)
 - 65fdb8 Minor clean up in life_of.md (#1608)
 - e53aff Add storage_texture,usage test to createVindGroup.spec.ts (#1813)
 - 39f597 Add `smoothstep` F32 Tests (#1811)
 - e97d14 Add tests to fullI32Range (#1792)
 - 7c4e02 Remove old implementation of correctlyRounded (#1796)
 - e93c41 Add 'multisampled_validation' test to createBindGroup.spec.ts (#1810)
 - cc7a40 Use trackForCleanup() for dst texture in copyToTexture cases (#1809)
 - 3c353f Adds remaining adapter.requestDevice tests. (#1798)
 - fd9cf4 Implement 'texture_buffer_usage' test to buffer_texture_copies.spec.ts (#1807)
 - f7f601 Add RENDER_ATTACHMENT usage when creating multisampled textures (#1806)
 - 63c716 Add 'texture_buffer_usage' test to buffer_texture_copies.spec.ts (#1803)

Created with './tools/run cts roll'

Change-Id: I608a519f30d75d18efd9edb6b1ece61e856ac2f5
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/+/101681
Auto-Submit: Ben Clayton <bclayton@google.com>
Commit-Queue: Austin Eng <enga@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Austin Eng <enga@chromium.org>

2022-09-09 16:14:19 +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 test list to deps

2022-08-11 15:16:38 +00:00

expectations.txt

Roll third_party/webgpu-cts/ 27dc745ca..a6451cc67 (19 commits)

2022-09-09 16:14:19 +00:00

README.md

Add CTS telemetry harness support

2022-03-24 00:21:55 +00:00

test_page.html

Change base directory for CTS runner, part 2

2022-06-24 18:50:19 +00:00

test_runner.js

CTS: Hook into CTS heartbeat mechanism instead of wrapping TestCaseRecorder

2022-08-26 22:34:27 +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.