Intermittent TEST-UNEXPECTED-TIMEOUT | toolkit/mozapps/update/tests/unit_aus_update/languagePackUpdates.js | Test timed out
Categories
(Thunderbird :: Upstream Synchronization, defect, P5)
Tracking
(thunderbird_esr78 unaffected)
Tracking | Status | |
---|---|---|
thunderbird_esr78 | --- | unaffected |
People
(Reporter: intermittent-bug-filer, Assigned: darktrojan)
References
Details
(Keywords: intermittent-failure)
Attachments
(1 file)
Filed by: geoff [at] darktrojan.net
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=311961906&repo=comm-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/fPKKCWVrQGaXTMqVvSPGPQ/runs/0/artifacts/public/logs/live_backing.log
This is caused by bug 1647443 but I'm not sure why it doesn't work for us.
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 2•4 years ago
|
||
Dave, can you offer any insight as to why this test would fail on Thunderbird, or if we should even be running it?
Comment 3•4 years ago
|
||
I think you should be running it. It looks like for some reason the test is going on to stage the update rather than stopping after downloading and so it sends out the wrong observer notification. It looks like I may have mistakenly thought that staging is disabled by default in xpcshell tests but I see some of the tests explicitly disabling it. That might be the fix. But then I'm not sure why Firefox is behaving differently here.
Assignee | ||
Comment 4•4 years ago
|
||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
You're right, and that's set to true in the default preferences, which for some reason get read during Thunderbird XPCShell tests but not in Firefox ones.
Comment hidden (Intermittent Failures Robot) |
Comment 7•4 years ago
|
||
Why? That's good old bug 1168178... so the app.update.staging.enabled true pref in firefox.js is not used.
Comment 8•4 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #7)
Why? That's good old bug 1168178... so the app.update.staging.enabled true pref in firefox.js is not used.
Sure, that's what I expected. What I don't understand is why are the Thunderbird prefs being used in this case?
Comment 9•4 years ago
|
||
Because Thunderbird does run xpcshell tests with normal app profile, so the app.update.staging.enabled true in all-thunderbird.js gets picked up.
We'd miss a lot of needed adjustments if we didn't use that, but it's of course unfortunate - for us, and I think in general too - that Firefox doesn't as well.
Updated•4 years ago
|
Comment 10•4 years ago
|
||
Comment hidden (Intermittent Failures Robot) |
Comment 12•4 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Updated•4 years ago
|
Description
•