| commit | 9e2aabee2d46b9cfb18864d5b9ec6e4ed7c0b9de | [log] [tgz] |
|---|---|---|
| author | John Stiles <johnstiles@google.com> | Tue Mar 12 20:52:23 2024 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Tue Mar 12 21:08:25 2024 |
| tree | b8ed16416b541c99991ad0a906e08b344c84c320 | |
| parent | 7557e87f6686cb37c27cb789d49d91c7630bdad5 [diff] |
Reland "Migrate Canvas WebGPU Access tests into WebGPU test directory." This reverts commit 6798b54bb4d0cbe4b012773b19437531462022fc. Reason for revert: errors caused by test-execution reordering should be fixed now that https://crrev.com/c/5362365 has landed Original change's description: > Revert "Migrate Canvas WebGPU Access tests into WebGPU test directory." > > This reverts commit 6c77ac02651792a760cc775c1ef5a2981654e9ba. > > Reason for revert: mysterious failures in `wpt_internal/webgpu/web_platform/reftests/canvas_composite_alpha_rgba16float_opaque_copy.https.html` since landing > > > Original change's description: > > Migrate Canvas WebGPU Access tests into WebGPU test directory. > > > > The Chromium CQ doesn't enable WebGPU when running the Canvas2D tests > > in wpt/external, so the tests can't live there. The WebGPU team has > > an internal directory that they use for testing which we can use here > > instead. > > > > We can no longer use the canvas Jinja/YAML framework to assemble > > tests outside of the external html/canvas directory, so I've > > cobbled together plain HTML pages for these tests instead. > > Fortunately the boilerplate is pretty minimal, since we can still > > rely on testharness.js. > > > > Bug: 41490345 > > Change-Id: I4cec7a1a65a04c850ec896adad359a28f93aaff8 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5356238 > > Commit-Queue: John Stiles <johnstiles@google.com> > > Auto-Submit: John Stiles <johnstiles@google.com> > > Reviewed-by: Kai Ninomiya <kainino@chromium.org> > > Commit-Queue: Kai Ninomiya <kainino@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#1271074} > > Bug: 41490345 > Change-Id: I608b5784bd81128d44de4462365c654b4426e8e2 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5361490 > Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Auto-Submit: John Stiles <johnstiles@google.com> > Cr-Commit-Position: refs/heads/main@{#1271185} Bug: 41490345 Bug: 329003665 Change-Id: Ic66e0d31a59a1c3a6d9b4e4317bb62514d55207c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5366765 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: John Stiles <johnstiles@google.com> Cr-Commit-Position: refs/heads/main@{#1271772}
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
wpt:matrix.org matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune (or git fetch -p && git merge).
See the documentation website and in particular the system setup for running tests locally.
The wpt command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve - For starting the wpt http serverwpt run - For running tests in a browserwpt lint - For running the lint against all testswpt manifest - For updating or generating a MANIFEST.json test manifestwpt install - For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave - For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt commands must be prefixed with python or the path to the python binary (if python is not in your %PATH%).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false in your working tree.
The master branch is automatically synced to wpt.live and w3c-test.org.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic../wpt lint as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!