commit | fee47672dc1e53e44346207bf4cb17fc9dc92cc0 | [log] [tgz] |
---|---|---|
author | Luke Zielinski <lpz@chromium.org> | Tue Feb 23 15:52:35 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 23 15:52:35 2021 |
tree | 87568e94ecfae2dccc156b944904e00d2ee7827b | |
parent | 18d26de42f76dd45a7102a84a09a92ecdc080185 [diff] |
Manually importing WPT tests. This recovers the auto-import from crrev.com/c/2712438 and rolls back the webdriver bidi changes, due to crbug.com/1180409. It also adjusts expectations and baselines for two flaky tests. Import wpt@f70aca56a3e5be65fd4d67ee64ca5dbb3ee9413b Using wpt-import in Chromium d163fd7c6905e456501aba914a24c20b62b4c6dc. With Chromium commits locally applied on WPT: 5d9c072f2e "Set resource requests' parameters for module service workers scripts." Note to sheriffs: 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/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: nzolghadr@chromium.org, mustaq@chromium.org: external/wpt/pointerevents NOAUTOREVERT=true No-Export: true Cq-Include-Trybots: luci.chromium.try:linux-wpt-identity-fyi-rel,linux-wpt-input-fyi-rel Change-Id: I95eeee01b64e90dbc9f48f4edd353d66733e48d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2713469 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Luke Z <lpz@chromium.org> Cr-Commit-Position: refs/heads/master@{#856697}
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.