Closed Bug 667884 Opened 8 years ago Closed 7 years ago

Intermittent timeout in browser/base/content/test/tabview/browser_tabview_dragdrop.js | application timed out after 330 seconds with no output

Categories

(Firefox Graveyard :: Panorama, defect)

x86
Windows XP
defect
Not set

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ttaubert, Unassigned)

References

Details

(Keywords: intermittent-failure)

TBSAUNDE
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1305176231.1305177452.16084.gz
Rev3 WINNT 5.1 mozilla-central opt test mochitest-other on 2011/05/11 21:57:11

s: talos-r3-xp-051
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_dragdrop.js | application timed out after 330 seconds with no output
PROCESS-CRASH | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_dragdrop.js | application crashed (minidump found)
Thread 29 (crashed)
TBSAUNDE
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1305176231.1305177452.16084.gz
Rev3 WINNT 5.1 mozilla-central opt test mochitest-other on 2011/05/11 21:57:11

s: talos-r3-xp-051
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_dragdrop.js | application timed out after 330 seconds with no output
PROCESS-CRASH | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_dragdrop.js | application crashed (minidump found)
Thread 29 (crashed)
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
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.