commit | d64fcfd3b7596fbf469eed90ed114eb8731ca26a | [log] [tgz] |
---|---|---|
author | Mikel Astiz <mastiz@chromium.org> | Tue Oct 17 10:06:40 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 17 10:06:40 2023 |
tree | be194ab9a5938e6d3a2548cee89a97f6344dd4ca | |
parent | c13aac2daf66d04d51e4329045130eee1191a08b [diff] |
Reland "[signin] Add more details to suspicious VLOG" This is a reland of commit 4e32eedb5a3a0345c6a0281731e367bf42ca2fd4, scoped down to less information in the log trace to avoid test timeouts (that required reverting the original patch). Original change's description: > [signin] Add more details to suspicious VLOG > > Some flaky test failures run into this VLOG, which is generally not > expected and also not present in successful runs. > > To understand better what triggers this codepath, the VLOG is extended > with more detailed information. > > Change-Id: Ib5fbd2f7cd3dc39c083803997d0fe64e12d8a318 > Bug: 1491558 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4935119 > Reviewed-by: David Roger <droger@chromium.org> > Commit-Queue: Mikel Astiz <mastiz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1209458} Bug: 1491558 Change-Id: Ic762dce71add0732c1a388cc2dc24cc208042dbe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4942166 Reviewed-by: David Roger <droger@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Auto-Submit: Mikel Astiz <mastiz@chromium.org> Commit-Queue: David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/main@{#1210735}
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.