commit | bae0bb5685c85120638ca86fb5c6ce1d097e7dd9 | [log] [tgz] |
---|---|---|
author | Peter Birk Pakkenberg <pbirk@chromium.org> | Mon Jun 24 09:16:51 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 24 09:16:51 2024 |
tree | d171180948b56fe8b445e9f24c593edd78312a43 | |
parent | b50479c8083199055d11ff80890a3a867d5ef2c6 [diff] |
Reland "Re-enable CTS testLoadUrl on Android 11+" This is a reland of commit 93c0bdf16d30eddd02b086ee6436900b70460f57 It only attempts to reland on 11+ as the CTS fix does not appear to have been made available on the 10 test runner. Original change's description: > Re-enable CTS testLoadUrl on Android 10+ > > The test was fixed in aosp/2613090, which should now be available on the > test runners. > > Fixed: 40915184 > Change-Id: I10e9f5705c0fa25edc7bd38258e4c14cddfabcb8 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5589109 > Reviewed-by: Nate Fischer <ntfschr@chromium.org> > Auto-Submit: Peter Pakkenberg <pbirk@chromium.org> > Commit-Queue: Nate Fischer <ntfschr@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1308822} Change-Id: I849d2105d32bf4dc97dfc89d869900a185d2c7c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5640158 Reviewed-by: Nate Fischer <ntfschr@chromium.org> Commit-Queue: Peter Pakkenberg <pbirk@chromium.org> Cr-Commit-Position: refs/heads/main@{#1318475}
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.