commit | 6a8e80f4235541484681a848f0bb7d9f28342d39 | [log] [tgz] |
---|---|---|
author | Jiaming Cheng <jiamingc@chromium.org> | Thu Jan 19 23:02:39 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 19 23:02:39 2023 |
tree | 7e3e85bc836b8174a3b5f039763cf0b73b5e4f07 | |
parent | 46616e0ee2a040e8b5f157a67f6577105e666d3f [diff] |
Revert "Fix HintsFetcherBrowserTest.ClearFetchedHints test to check navigation hints status rather than hint loaded because store is flaky" This reverts commit 5e8429bafb3e8990d54e44d8d9c275df1347e437. Reason for revert: This test kept failing on https://ci.chromium.org/p/chromium/builders/ci/linux-lacros-tester-rel See more details: https://ci.chromium.org/ui/p/chromium/builders/ci/linux-lacros-tester-rel/39503/overview Original change's description: > Fix HintsFetcherBrowserTest.ClearFetchedHints test to check navigation hints status rather than hint loaded because store is flaky > > Bug: 1166906,b/266096305 > Change-Id: Idc191c3ec12aba3cdbf436454213bd269e6ba3cf > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4181486 > Reviewed-by: Raj T <rajendrant@chromium.org> > Auto-Submit: Sophie Chang <sophiechang@chromium.org> > Commit-Queue: Raj T <rajendrant@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1094656} Bug: 1166906,b/266096305 Change-Id: Iae0d05c199ef6a4350fd3a23a123a271e5c984b1 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4182741 Commit-Queue: Sophie Chang <sophiechang@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Sophie Chang <sophiechang@chromium.org> Cr-Commit-Position: refs/heads/main@{#1094735}
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.