Intermittent testActivityStreamContextMenu | application timed out after 180 seconds with no output

RESOLVED INCOMPLETE

Status

()

P3
normal
RESOLVED INCOMPLETE
2 years ago
a year ago

People

(Reporter: intermittent-bug-filer, Unassigned)

Tracking

({bulk-close-intermittents, intermittent-failure})

Firefox Tracking Flags

(Not tracked)

Details

This test was just enabled in bug 1330280.
Flags: needinfo?(s.kaspari)
(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)
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.
(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.
Priority: -- → P3
Status: NEW → RESOLVED
Last Resolved: a year ago
Keywords: bulk-close-intermittents
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.