| commit | c9f93b92d8314d6560e3cb39ff125a6c3ab9afd8 | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Jul 14 02:46:21 2022 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 14 02:46:21 2022 |
| tree | 06274f6dcc8b77886f908e684ba9d49cb1eccc71 | |
| parent | 22e89eaa55c467308b10ed14c440756042c576b4 [diff] |
Roll earl_grey2 from 2882ae6f9ac2 to 5bca387a7599 (1 revision) https://chromium.googlesource.com/external/github.com/google/EarlGrey.git/+log/2882ae6f9ac2..5bca387a7599 2022-07-14 albertbow@google.com Fix synchronization error message to remove ignored app state. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/earlgrey2-chromium Please CC lindsayw@chromium.org,zhaoyangli@chromium.org on the revert to ensure that a human is aware of the problem. To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs Bug: None Tbr: lindsayw@chromium.org,zhaoyangli@chromium.org Change-Id: I70519dfaa0665c5aea809b04996e45845911e6a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3761616 Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1024084}
ChromiumChromium 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.