New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 891362 link

Starred by 1 user
Status: WontFix
Owner:
tbansal@chromium.org
Closed: Dec 21
Cc:
skare@chromium.org
isherman@chromium.org
asvitk...@chromium.org
█ rkaplow@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Increase in number of UMA reports with connection_type set to AMBIGUOUS

Project Member Reported by tbansal@chromium.org, Oct 2 
Recently, there has been an increase in the number of UMA reports with connection_type set to AMBIGUOUS.
See https://uma.googleplex.com/p/chrome/timeline_v2/?sid=b4df343b7b139f6c54f115a99dc52f0c.

https://chromium.googlesource.com/chromium/src/+log/70.0.3508.0..70.0.3512.0?pretty=fuller&n=10000 looks like the possible commit range.

Comment 1 by tbansal@chromium.org, Nov 13 

Another screenshot showing the increase in Ambiguous: https://screenshot.googleplex.com/p9ggitDh1O3

Comment 2 by tbansal@chromium.org, Dec 19

Owner: tbansal@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by tbansal@chromium.org, Dec 19

Labels: -Pri-3 -M-70 RegressedIn-70 M-73 Pri-2

Comment 4 by tbansal@chromium.org, Dec 21

Labels: -M-73 M-72
Status: WontFix (was: Assigned)
I was trying to repro this, but I could not. After looking at the more recent UMA, it seems it got fixed in M-72. UMA  (https://screenshot.googleplex.com/YomVGophop0) shows that the AMBIGUOUS counts have dropped sharply. Likely commit range shows network service related changes in network_metrics_provider.cc. So, closing this bug since there is nothing left to do here.
►

Sign in to add a comment