646862 - Intermittent infinite loop of "ASSERTION: XPConnect is being called on a scope without a 'Components' property!" in browser/base/content/test/tabview/browser_tabview_privatebrowsing.js winding up with "command timed out: 5400 seconds elapsed"

Status: RESOLVED WORKSFORME

(Firefox Graveyard :: Panorama, defect, P3)

Description

[(no longer active)]

+++ This bug was initially created as a clone of Bug #631447 +++

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1301577704.1301584299.12840.gz&fulltext=1

I bet it's another clone of bug 631447, but filing for now.

Comment 1

[Kevin Hanes]

Adding to our Fx5 list until it's determined if this is a dupe or not

Comment 2

[Daniel Holbert [:dholbert]]

http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Beta/1305881834.1305889081.18436.gz
Rev3 WINNT 5.1 mozilla-beta debug test mochitest-other on 2011/05/20 01:57:14
s: talos-r3-xp-035

Comment 3

[Tim Taubert [:ttaubert] (inactive)]

bugspam

Comment 4

[Tim Taubert [:ttaubert] (inactive)]

bugspam

Comment 5

[Tim Taubert [:ttaubert] (inactive)]

Adding intermittent test failures to new meta bug.

(bugspam)

Comment 6

[Legacy TBPL/Treeherder Robot]

ehsan%mozilla.com
http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Inbound/1308678472.1308679870.27918.gz
Rev3 Fedora 12x64 mozilla-inbound opt test mochitest-other on 2011/06/21 10:47:52

s: talos-r3-fed64-057
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_privatebrowsing.js | Test timed out

Comment 7

[Tim Taubert [:ttaubert] (inactive)]

bugspam

(Fx7 was branched, removing open bugs from Fx7 meta bug, we won't create new meta bugs for upcoming Fx versions)

Comment 8

[Ed Morley [:emorley]]

Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500