Fix block type UMA |
||
Issue descriptionIt appears that DataReductionProxy.BlockTypeFallback and DataReductionProxy.BlockTypePrimary are reporting data that is inconsistent with other histograms tracking bypass. This appears to have changed around M51, and it appears that other bypass types might be reported as "Bypass due to a 4xx missing via header".
,
Jan 4 2017
I spent a while looking at this, and there are definitely some bugs, but I still don't understand what is causing all of the weirdness of this bug. 4xx should not be logged as a bypass since we don't bypass it at all, but that alone doesn't explain all of the problems.
,
Jan 5 2017
I found the problem that this data is really split over two histograms. DataReductionProxy.BlockTypePrimary and DataReductionProxy.BypassTypePrimary Same thing for the Fallback. There are still interesting problems with set last bypass type.
,
Jan 5 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by bengr@chromium.org
, Dec 22 2016Owner: ryansturm@chromium.org
Status: Assigned (was: Untriaged)