commit | dfe66da3b599fbfe4b7c26c4f36ec08d4499d656 | [log] [tgz] |
---|---|---|
author | Chromium WPT Sync <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Fri Mar 21 16:15:56 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 21 16:15:56 2025 |
tree | e1541e6850d4990928d4656bade3b1d5ce5d3578 | |
parent | b8ae7f317748a25d3297d28dc2345e9e7fd6c970 [diff] |
Import wpt@f67622eac150a74aed36a66a27c5d66cc39cb09d https://github.com/web-platform-tests/wpt/compare/f144120b7...f67622eac Using wpt-import in Chromium ec8907eea4310bd242180dfeea6bf97bc3f9a830. With Chromium commits locally applied on WPT: 883b14d87f "webnn: add fp16 conformance tests for activation [...] 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: If67b05888c6f19c79524878df8e7468943d1f7e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6382755 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@{#1436087}
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.