Closed Bug 577409 Opened 14 years ago Closed 12 years ago

Intermittent OS X 10.6 browser_aboutCrashesResubmit.js | Timed out (followed by Found an unexpected tab at the end of test run)

Categories

(Toolkit :: Crash Reporting, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure, regression)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1278539167.1278540066.30160.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test mochitest-other on
2010/07/07 14:46:07
s: talos-r3-snow-044

TEST-UNEXPECTED-FAIL |
chrome://mochikit/content/browser/toolkit/crashreporter/test/browser/browser_aboutCrashesResubmit.js
| Timed out
TEST-UNEXPECTED-FAIL |
chrome://mochikit/content/browser/toolkit/crashreporter/test/browser/browser_aboutCrashesResubmit.js
| Found an unexpected tab at the end of test run: about:crashes

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1278553069.1278555004.22720.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test mochitest-other on
2010/07/07 18:37:49
s: talos-r3-snow-003

TEST-UNEXPECTED-FAIL |
chrome://mochikit/content/browser/toolkit/crashreporter/test/browser/browser_aboutCrashesResubmit.js
| Timed out
TEST-UNEXPECTED-FAIL |
chrome://mochikit/content/browser/toolkit/crashreporter/test/browser/browser_aboutCrashesResubmit.js
| Found an unexpected tab at the end of test run: about:crashes
I tried running this test in a loop dozens of times and couldn't get it to fail locally. I ran the entire browser-chrome suite a few times in a loop and didn't see it there either. It's probably timing related (as usual), so my MBP is too fast to reproduce it.
Assignee: ted.mielczarek → nobody
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]
You need to log in before you can comment on or make changes to this bug.