commit | d4e61a16a3aec5937e2e54aeb46e65ca737aa608 | [log] [tgz] |
---|---|---|
author | Jonathan Lee <jonathanjlee@google.com> | Fri Feb 28 09:19:26 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 28 09:19:26 2025 |
tree | dd5e5f2ac051eabc2dca930fd692ae5fb2e62888 | |
parent | be660dce04ed913c6efed1114feafc1bd97aed9e [diff] |
[wpt] Remove stale expectations for passing wdspec tests Stale expectations were determined by eyeballing the test history in CI (e.g., [0]). This restores some coverage for `chromedriver`'s spec conformance. [0]: https://luci-milo.appspot.com/ui/test/chromium/ninja%3A%2F%2F%3Achrome_wpt_tests%2Fexternal%2Fwpt%2Fwebdriver%2Ftests%2Fbidi%2Fbrowsing_context%2Fcapture_screenshot%2Fformat.py?q=V%3Abuilder%3DLinux%2520Tests%2520%28dbg%29%281%29+V%3Aos%3DUbuntu-22.04+V%3Atest_suite%3Dwebdriver_wpt_tests Bug: 385032709, 324436866, 345118873, 324436866, 343338108 Change-Id: I45c9a18760078f6ad8abfdcc227e26d03a76080b Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Cq-Include-Trybots: luci.chromium.try:linux_chromium_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6310420 Auto-Submit: Jonathan Lee <jonathanjlee@google.com> Commit-Queue: Maksim Sadym <sadym@chromium.org> Reviewed-by: Maksim Sadym <sadym@chromium.org> Cr-Commit-Position: refs/heads/main@{#1426183}
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.