Closed Bug 667594 Opened 13 years ago Closed 12 years ago

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

Categories

(Firefox Graveyard :: Panorama, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ehsan.akhgari, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Inbound/1309191154.1309192431.11076.gz
Rev3 WINNT 5.1 mozilla-inbound opt test mochitest-other on 2011/06/27 09:12:34

TEST-START | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | There is one group item on startup
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | There should be two tab items in that group.
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | The currently selected tab should be the first tab in the groupItemOne
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | New tab button exists
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | The currently selected tab should be the only tab in the groupItemTwo
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | The currently selected tab should be the first tab in the groupItemOne
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | The currently selected tab should be the only tab in the groupItemTwo
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | The currently selected tab should be the second tab in the groupItemOne
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | application timed out after 330 seconds with no output
INFO | automation.py | Application ran for: 0:07:25.515000
INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmps3vuxipidlog
==> process 1096 launched child process 472
INFO | automation.py | Checking for orphan process with PID: 472
PROCESS-CRASH | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_bug590606.js | application crashed (minidump found)
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: 12 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.