Closed Bug 1342887 Opened 8 years ago Closed 8 years ago

Intermittent test_fallback_update.py TestFallbackUpdate.test_update | TimeoutException: Timed out after 300.1 seconds with message: Update has been applied.

Categories

(Toolkit :: Application Update, defect)

Unspecified
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla54
Tracking Status
firefox53 --- unaffected
firefox54 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: molly)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

This is an new issue which started recently for OS X and mozilla-central only. As it looks like around February the 18th. Matt and Rob, did we had changes to the updater lately, which could have caused a very long delay in applying the update? Here we run out of time after 300s.
Flags: needinfo?(robert.strong.bugs)
Flags: needinfo?(mhowell)
OS: Unspecified → Mac OS X
The only recent Mac-specific thing I know of was bug 1335916, but that landed on the 10th. Do you know of a way that could have started causing failures to appear around the 18th instead of the 10th?
Flags: needinfo?(mhowell)
The changes as done in this patch might indicate a possible hang like noticed on this bug. I had another look at Treeherder and noticed a gap between 17th and 13th of February. So the earliest test failure we have is from February 13th: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-searchStr=fxup-nightly%20os%20x&filter-tier=1&filter-tier=2&filter-tier=3&bugfiler&fromchange=4dfd0d2d5dd3b640d46ee405af7523e37545c155&selectedJob=76815040 Then no test failure until February 17th: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-searchStr=fxup-nightly%20os%20x&filter-tier=1&filter-tier=2&filter-tier=3&bugfiler&fromchange=4dfd0d2d5dd3b640d46ee405af7523e37545c155&selectedJob=78565274 Then another time with no failures and perma failure for at least the machine osx-10-10-2 since Tuesday. Btw. today David Burns also mentioned to me a hang during applying updates for Nightly on OS X, which forced him to kill Firefox. Maybe that has the same underlying issue.
Flags: needinfo?(robert.strong.bugs)
Don't close this bug immediately after landing this patch, because I'm not certain it will completely solve the problem. But at least the new logging might help.
Keywords: leave-open
Comment on attachment 8841741 [details] Bug 1342887 - Detect and log failures to dispatch SetupMacCommandLine to the main thread. https://reviewboard.mozilla.org/r/115874/#review117254
Attachment #8841741 - Flags: review?(robert.strong.bugs) → review+
Pushed by mhowell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3120e572493a Detect and log failures to dispatch SetupMacCommandLine to the main thread. r=rstrong
Matt, I haven't seen this test failure anymore for our update tests on central. So I assume that we can this marked as fixed? Would an uplift to aurora be helpful?
Flags: needinfo?(mhowell)
Assignee: nobody → mhowell
Status: NEW → ASSIGNED
Component: Firefox UI Tests → Application Update
Product: Testing → Toolkit
QA Contact: hskupin
Version: Version 3 → unspecified
Oh, checking the landed patch on hg.mo, this should actually have been fixed for 54.0.
Target Milestone: --- → mozilla54
Sure, if you're not seeing this failure anymore, then I'd say this bug is resolved. I'll mark it as such.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(mhowell)
Resolution: --- → FIXED
Removing leave-open keyword from resolved bugs, per :sylvestre.
Keywords: leave-open
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: