mochitest timeout in browser_history_sidebar_search.js ==> TIMEOUT, NOT FAILURE! <==

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
10 years ago
7 years ago

People

(Reporter: jfkthame, Unassigned)

Tracking

({intermittent-failure})

Firefox Tracking Flags

(Not tracked)

Details

Seen on tinderbox, couldn't find an existing bug:

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1262943606.1262945522.11168.gz
WINNT 5.2 mozilla-central opt test everythingelse on 2010/01/08 01:40:06
s: win32-slave31

Waiting for window activation...
Running chrome://mochikit/content/browser/browser/components/places/tests/browser/browser_history_sidebar_search.js...
TEST-INFO | chrome://mochikit/content/browser/browser/components/places/tests/browser/browser_history_sidebar_search.js | Console message: [JavaScript Error: "this.treeBoxObject.view is null" {file: "chrome://browser/content/places/tree.xml" line: 37}]
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/components/places/tests/browser/browser_history_sidebar_search.js | Timed out

There are possibly similar history sidebar timeout issues in bug 532842 and bug 507172, though not on this particular test, hence filing this separately.
maybe related to bug 537507?

btw, it's the first time i see this failure.
Blocks: 438871
Whiteboard: [orange]
the last correct report in this bug is comment 2, any other report here is wrong and is instead bug 575132.

We don't see timeouts from quite some time. resolving.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Summary: mochitest timeout in browser_history_sidebar_search.js → mochitest timeout in browser_history_sidebar_search.js ==> TIMEOUT, NOT FAILURE! <==
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.