Closed Bug 1015892 Opened 10 years ago Closed 10 years ago

Permanent orange: TEST-UNEXPECTED-FAIL | test_metadata_update.js | (head.js NS_ERROR_UNEXPECTED getIntPref)

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla32
Tracking Flags:
Tracking Status
firefox30 --- unaffected
firefox31 --- unaffected
firefox32 --- fixed
firefox-esr24 --- unaffected

People

(Reporter: standard8, Assigned: Irving)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

Override the metadata ping URL pref so we don't try to contact AMO
2.07 KB, patch
Unfocused
: review+
Details | Diff | Splinter Review 
On trunk:

1401069444069	DeferredSave.extensions.json	DEBUG	Write succeeded
1401069444069	addons.xpi-utils	DEBUG	XPI Database saved, setting schema version preference to 16
1401069444390	addons.repository	DEBUG	Got metadata search load event
1401069444390	addons.repository	WARN	Search failed when repopulating cache
1401069444391	addons.xpi	DEBUG	updateAddonRepositoryData found 1 visible add-ons
TEST-INFO | /builds/slave/talos-slave/test/build/xpcshell/tests/toolkit/mozapps/extensions/test/xpcshell/test_metadata_update.js | "Update done, getting last update"
TEST-UNEXPECTED-FAIL | /builds/slave/talos-slave/test/build/xpcshell/head.js | Unexpected exception NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getIntPref]
TEST-INFO | (xpcshell/head.js) | exiting test

Interesting parts:

- Search of the cache fails after repopluating the add-on cache. This causes the extensions.getAddons.cache.lastUpdate pref not to be set, which in turn causes the exception seen in the failure.

- Disabling build of lightning doesn't seem to help

- Bug 760356 added this as a new test
Status: NEW → ASSIGNED
QA Contact: irving
Bah, the test I added in bug 760356 was trying to reach services.a.m.o for a metadata ping; fixed the test to override the url and not use a static port number.
Assignee: nobody → irving
Attachment #8429329 - Flags: review?(bmcbride)
try build of an earlier version of the patch that still had static port #: https://tbpl.mozilla.org/?tree=Thunderbird-Try&rev=b1c3463d7778
QA Contact: irving
Comment on attachment 8429329 [details] [diff] [review]
Override the metadata ping URL pref so we don't try to contact AMO

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

Oops, I should have caught that.
Attachment #8429329 - Flags: review?(bmcbride) → review+
https://hg.mozilla.org/integration/fx-team/rev/f05d51941f4c
Component: General → Add-ons Manager
Product: Thunderbird → Toolkit
Whiteboard: [fixed-in-fx-team]
https://hg.mozilla.org/mozilla-central/rev/f05d51941f4c
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → mozilla32
You need to log in before you can comment on or make changes to this bug.