Closed
Bug 1332418
Opened 7 years ago
Closed 7 years ago
Intermittent testActivityStreamContextMenu | application timed out after 180 seconds with no output
Categories
(Firefox for Android Graveyard :: Testing, defect, P3)
Firefox for Android Graveyard
Testing
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: bulk-close-intermittents, intermittent-failure)
Filed by: philringnalda [at] gmail.com https://treeherder.mozilla.org/logviewer.html#?job_id=70350930&repo=autoland https://queue.taskcluster.net/v1/task/NJNvtfzdRE6wg_Scc_Mduw/runs/0/artifacts/public/logs/live_backing.log
Comment 2•7 years ago
|
||
(In reply to Geoff Brown [:gbrown] from comment #1) > This test was just enabled in bug 1330280. Re-enabled. After roughly a week being disabled because I needed to refactor the code. The test does more or less some database queries and looking at the log this seems to be a random crash before the test even really started?
Flags: needinfo?(s.kaspari)
Comment 3•7 years ago
|
||
One thing that might be odd (but not sure if this could cause the issue here) is that I do some database cleanup pretty early in setUp() while the main test waits for blockForGeckoReady(); before it does anything. Maybe it makes sense to do the cleanup inside the test method after waiting for Gecko.
Comment 4•7 years ago
|
||
(In reply to Sebastian Kaspari (:sebastian) from comment #2) > The test does more or less some database queries and looking at the log this > seems to be a random crash before the test even really started? Firefox was killed by the test harness after a timeout. The main log is a little misleading, but the logcat shows the test running. "Top Sites cursor is not null" seems to be the last message.
Updated•7 years ago
|
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 7 years ago
Keywords: bulk-close-intermittents
Resolution: --- → INCOMPLETE
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•