Closed Bug 1400791 Opened 7 years ago Closed 5 years ago

Intermittent test_fallback_update.py TestFallbackUpdate.test_update | application crashed [@ RunWatchdog]

Categories

(Testing :: Firefox UI Tests, defect, P5)

Version 3
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, intermittent-failure)

Crash Data

This is a hang during shutdown. Maybe related to the staging updates we do with the tests? Robert might know more given that he disabled those across all platforms lately.
Flags: needinfo?(robert.strong.bugs)
(In reply to Treeherder Bug Filer from comment #0)
> Appears to have been introduced in:
> https://treeherder.mozilla.org/#/jobs?repo=mozilla-
> central&revision=45b63125a4301eb89e7a4d70d0da1c650f11c7e4&filter-
> tier=1&filter-tier=2&filter-tier=3

Please note that this update job has a build number of 3, which means that the source build is from 13th, and the regression could have been caused by any changes between Sep 12th and 13th.
Maybe this could be a dupe of bug 1399601 which also started recently on Linux. It's not for update tests, but also related to a restart of Firefox.
(In reply to Henrik Skupin (:whimboo) from comment #3)
> Maybe this could be a dupe of bug 1399601 which also started recently on
> Linux. It's not for update tests, but also related to a restart of Firefox.
bug 1399601 sounds likely.
Flags: needinfo?(robert.strong.bugs)
Maybe we see that because the tests enable update staging, which we don't use at the moment when offering users updates of Firefox. I want to note that we cannot easily turn that off, because the tests would need to be updated too given that they don't support the non-staging update path yet.
Maybe but doubtful especially since that bug occurs without update staging.
Meant to say "without updating".

We don't run the update tests anymore. So there won't be updates for this bug.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.