commit | 42bc84fb9ea68d6eea84718c35f9c81c25363ec4 | [log] [tgz] |
---|---|---|
author | sophiewen <sophiewen@chromium.org> | Mon Sep 25 20:55:26 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 25 20:55:26 2023 |
tree | bcc1404e063a9714517adea6bd9ff8664632fe7e | |
parent | a442f1e185dd531ec75f2135791e6cb6bf0f32ce [diff] |
Reland "snap-groups: Record snap two windows duration" This is a reland of commit 21ab723529a531aa00d927eeebbde38792aaa6d2 Fixed broken tests in https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20ChromiumOS%20MSan%20Tests/38477/overview. Original change's description: > snap-groups: Record snap two windows duration > > This adds metrics that will be used by Snap Groups. We want to record > the distribution of users snapping a first window then a second window > on the opposite side within X minutes, where X is very low. > > If the first window is unsnapped or closed without a second window > getting snapped, we will record it as very high, i.e. the max bucket. > > Note that this ignores partial ratios, if a user for some reason snaps > mismatched ratios (e.g. 2/3 left and 1/2 right), it will be recorded. > > Test: added > Fixed: b/299666829 > Change-Id: I1d070466b2fb89971fef988aadcfe133eb46d49a > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4854503 > Reviewed-by: Sammie Quon <sammiequon@chromium.org> > Commit-Queue: Sophie Wen <sophiewen@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1197947} Change-Id: Iecdd46c4b31d311a0d463fcac3f48490979bb337 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4883810 Reviewed-by: Yulun Wu <yulunwu@chromium.org> Commit-Queue: Sophie Wen <sophiewen@chromium.org> Reviewed-by: Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/main@{#1201139}
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.