commit | 32db99c3df96f50d667054cdc6a284d1d21db60c | [log] [tgz] |
---|---|---|
author | Chromium WPT Sync <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Mon Jul 01 04:09:10 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 01 04:09:10 2024 |
tree | a4d264681c69d5d24d6e1cf2607a2b07fb2152f6 | |
parent | fa70c225179a9e866827a8f958649c6c3cb6e9d2 [diff] |
Import wpt@c267e5afc956cf18849a30aa4faf0eb3d3031a5d https://github.com/web-platform-tests/wpt/compare/639fa5369...c267e5afc Using wpt-import in Chromium 5d767292566fc8a703add425aec266384201f481. With Chromium commits locally applied on WPT: 75dc56200d "webnn: update validation_tests to use opSupportLimits" Note to gardeners: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md NOAUTOREVERT=true R=rubber-stamper@appspot.gserviceaccount.com No-Export: true Validate-Test-Flakiness: skip Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Change-Id: Idbef84b624038a82aceb9998d89b18cf7670462d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5666179 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1321508}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.