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

Issue 756116 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Resumption records multiple Download.InterruptReason

Project Member Reported by xingliu@chromium.org, Aug 16 2017

Issue description

During metric meeting, we have discussed about auto resumption records multiple Download.InterruptReason.

Should we only record the first error instead of every error in the retry?

Or we can separate the error in the retry to another histogram, and Download.InterruptReason only records the first error. 

There is also discussion about the retry errors can be different from the first error. So I think another histogram like Download.AutoResumption.InterruptReason probably makes sense.
 
Cc: dah...@chromium.org
So maybe we need something else?  Do we really want the first interrupt reason if we're resuming?  If we do that I'm worried we won't be able to tell what the final outcome of the download was.
Status: WontFix (was: Assigned)
As discussed in meeting, marked this as won't fix.

Sign in to add a comment