Closed Bug 1090450 Opened 10 years ago Closed 10 years ago

Add-on background update always skipped

Categories

(Toolkit :: Add-ons Manager, defect)

x86
All
defect
Not set
major

Tracking

()

RESOLVED FIXED
mozilla36
Tracking Status
firefox34 + fixed
firefox35 + fixed
firefox36 + fixed

People

(Reporter: jryans, Assigned: jryans)

References

Details

(Keywords: regression)

Attachments

(1 file, 1 obsolete file)

Each time the background add-on update timer is reached, my add-ons do not update.

I investigated this by enabling "extensions.logging.enabled", and setting "extensions.update.interval" to a low value, and got the message:

"Skipping background update check"

every update interval.

It appears this was introduced by bug 995108 with a subtly broken refactoring.
This resolves the issue for me.

If you have suggestions on where to test this, I am happy to add it.  I haven't looked at Add-on Manager ever before, so I am not really sure where would be good.
Attachment #8512924 - Flags: review?(dtownsend+bugmail)
Comment on attachment 8512924 [details] [diff] [review]
Properly check add-on update state during update interval

Review of attachment 8512924 [details] [diff] [review]:
-----------------------------------------------------------------

test_backgroundupdate.js should be verifying this but it now bypasses all the checks to force the update check to happen. Instead of calling AddonManagerPrivate.backgroundUpdateCheck directly we could have it call the addonManager.js component as an nsITimerCallback.

Bonus points for extending it to check the various different cases for having updates enabled but I'll take the simple test fix for now.
Attachment #8512924 - Flags: review?(dtownsend+bugmail) → review+
OS: Mac OS X → All
Added the simple test fix to use the timer callback.

I verified that the updated test would fail without the bug fix.

Try: https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=46d68ea32c4e
Attachment #8512924 - Attachment is obsolete: true
Attachment #8513206 - Flags: review+
https://hg.mozilla.org/integration/fx-team/rev/bd13f6891f4f
Flags: in-testsuite+
Keywords: checkin-needed
Whiteboard: [fixed-in-fx-team]
https://hg.mozilla.org/mozilla-central/rev/bd13f6891f4f
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → mozilla36
jryans is on pto today. Assuming this is good on m-c, what do you think about uplifting to 34 and 35, which are both marked as affected?
Flags: needinfo?(dtownsend+bugmail)
Comment on attachment 8513206 [details] [diff] [review]
Properly check add-on update state during update interval (v2, Mossop: r+)

Yes. Let's uplift this bug.

Approval Request Comment
[Feature/regressing bug #]: regression: bug 995108 
[User impact if declined]: Addons are not auto-updated
[Describe test coverage new/current, TBPL]: in m-c
[Risks and why]: Low. Small patch.
[String/UUID change made/needed]: none
Flags: needinfo?(dtownsend+bugmail)
Attachment #8513206 - Flags: approval-mozilla-beta?
Attachment #8513206 - Flags: approval-mozilla-aurora?
Yes, absolutely
Comment on attachment 8513206 [details] [diff] [review]
Properly check add-on update state during update interval (v2, Mossop: r+)

Beta+
Aurora+
Attachment #8513206 - Flags: approval-mozilla-beta?
Attachment #8513206 - Flags: approval-mozilla-beta+
Attachment #8513206 - Flags: approval-mozilla-aurora?
Attachment #8513206 - Flags: approval-mozilla-aurora+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: