Closed
Bug 1151267
Opened 9 years ago
Closed 9 years ago
app update telemetry for UPDATE_CANNOT_APPLY_* is reversed
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
FIXED
mozilla40
Tracking | Status | |
---|---|---|
firefox37 | --- | unaffected |
firefox38 | --- | unaffected |
firefox39 | --- | fixed |
firefox40 | --- | fixed |
firefox-esr31 | --- | unaffected |
firefox-esr38 | --- | unaffected |
People
(Reporter: robert.strong.bugs, Assigned: robert.strong.bugs)
Details
Attachments
(1 file)
7.53 KB,
patch
|
spohl
:
review+
lizzard
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
The telemetry reports true when the user can apply updates.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → robert.strong.bugs
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•9 years ago
|
||
Assignee | ||
Comment 2•9 years ago
|
||
Comment on attachment 8589905 [details] [diff] [review] patch rev1 try push https://treeherder.mozilla.org/#/jobs?repo=try&revision=ac9cf2a1d972
Attachment #8589905 -
Attachment description: patch in progress → patch rev1
Attachment #8589905 -
Flags: review?(spohl.mozilla.bugs)
Comment 3•9 years ago
|
||
Comment on attachment 8589905 [details] [diff] [review] patch rev1 Review of attachment 8589905 [details] [diff] [review]: ----------------------------------------------------------------- Looks good, just one question before I can r+ this. ::: toolkit/mozapps/update/nsUpdateService.js @@ -1439,5 @@ > break; > case STATE_PENDING: > stateCode = 4; > - parts[0] = STATE_FAILED; > - parts.push(STAGE_FAIL_FALLBACK); Was this meant to be removed in this patch? If so, could you give me some context why we want to remove this here?
Assignee | ||
Comment 4•9 years ago
|
||
Because the state code of STATE_PENDING provides the same info already. I need to come up with a way to report the specific error which I'll do in another bug
Assignee | ||
Comment 5•9 years ago
|
||
Does my reply in comment #4 make sense?
Flags: needinfo?(spohl.mozilla.bugs)
Comment 6•9 years ago
|
||
Is it safe to assume that not having parts[0] set to STATE_FAILED will not cause other incorrect behavior? For example, if parts[0] is not set to STATE_FAILED in refreshUpdateStatus, we don't seem to call handleFallbackToCompleteUpdate [1]. Do we care? [1] http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/update/nsUpdateService.js#3349
Flags: needinfo?(spohl.mozilla.bugs)
Assignee | ||
Comment 7•9 years ago
|
||
(In reply to Stephen Pohl [:spohl] from comment #6) > Is it safe to assume that not having parts[0] set to STATE_FAILED will not > cause other incorrect behavior? For example, if parts[0] is not set to > STATE_FAILED in refreshUpdateStatus, we don't seem to call > handleFallbackToCompleteUpdate [1]. Do we care? > > [1] > http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/update/ > nsUpdateService.js#3349 The only place this is changed is in pingStateAndStatusCodes, the only thing this change affects is the telemetry ping, and this is intentional. This makes it so it doesn't report the "custom" error of 97 when the state is STATE_PENDING when calling pingStatusErrorCode. Of course we care and in this case the change is the right thing to do. It isn't something we had at some point in the past. Can you point to some code where this change might cause some problem?
Flags: needinfo?(spohl.mozilla.bugs)
Comment 8•9 years ago
|
||
Comment on attachment 8589905 [details] [diff] [review] patch rev1 Thanks, this makes sense now!
Flags: needinfo?(spohl.mozilla.bugs)
Attachment #8589905 -
Flags: review?(spohl.mozilla.bugs) → review+
Assignee | ||
Comment 9•9 years ago
|
||
Pushed to fx-team https://hg.mozilla.org/integration/fx-team/rev/5949612d030a
Target Milestone: --- → mozilla40
Assignee | ||
Comment 11•9 years ago
|
||
Comment on attachment 8589905 [details] [diff] [review] patch rev1 Approval Request Comment [Feature/regressing bug #]: Bug 1137447 [User impact if declined]: It will be more difficult to analyze telemetry for app update which helps to identify areas where we need to improve. [Describe test coverage new/current, TreeHerder]: None [Risks and why]: Little to none. Tested locally. The code wraps the calls in try blocks to prevent it from breaking app update. It has also been on m-c. [String/UUID change made/needed]: None
Attachment #8589905 -
Flags: approval-mozilla-aurora?
Comment 12•9 years ago
|
||
Comment on attachment 8589905 [details] [diff] [review] patch rev1 Approving for uplift to aurora. This has had a day on m-c and seems low risk.
Attachment #8589905 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Assignee | ||
Comment 13•9 years ago
|
||
Pushed to mozilla-aurora https://hg.mozilla.org/releases/mozilla-aurora/rev/7f06e1d0445d
status-firefox37:
--- → unaffected
status-firefox38:
--- → unaffected
status-firefox39:
--- → fixed
status-firefox-esr31:
--- → unaffected
status-firefox-esr38:
--- → unaffected
You need to log in
before you can comment on or make changes to this bug.
Description
•