commit | c39f3cb9b2e905d4609a4e7c04c8de8c3883faf8 | [log] [tgz] |
---|---|---|
author | Chromium WPT Sync <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Wed Jan 15 20:31:45 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 15 20:31:45 2025 |
tree | 9fb7a3660b250912756e0636747e07686e9d3192 | |
parent | 6ead50d46b7747ae7734f3c2886d1c180325ef97 [diff] |
Import wpt@bd1e58070c179189efc1e6f0561d4302cfdbc468 https://github.com/web-platform-tests/wpt/compare/e26477f97...bd1e58070 Using wpt-import in Chromium 960378c4e2954c05fb19982dd1ebbf4ff4cc2e7c. With Chromium commits locally applied on WPT: d7e7a1e38e "webnn: add fp16 conformance tests for element-wise [...] 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 Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Change-Id: Ia30810ab3ddfadd43711673f37146e1d1ae4b6fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6176160 Auto-Submit: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1406901}
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.