Closed Bug 582163 Opened 16 years ago Closed 13 years ago

Intermittent failure in test_form_submission_cap2.html | Test timed out

Categories

(Toolkit :: Form Manager, defect)

Product:
Toolkit
Component:
Form Manager
Platform:
x86
Windows Server 2003
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mossop, Unassigned)

References

Details

(Keywords: intermittent-failure)

WINNT 5.2 mozilla-central opt test mochitests-5/5 on 2010/07/26 20:36:01 http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1280201761.1280202782.1016.gz 6422 INFO TEST-START | /tests/toolkit/components/satchel/test/test_form_submission_cap2.html 6423 INFO TEST-PASS | /tests/toolkit/components/satchel/test/test_form_submission_cap2.html | Got formHistory service 6424 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/components/satchel/test/test_form_submission_cap2.html | Test timed out. 6425 INFO SimpleTest finished /tests/toolkit/components/satchel/test/test_form_submission_cap2.html in 304651ms
Next expected line of output should be "checking for initially empty storage", so either the page's |load| event never fired, or the test hung in the (trivial) call to fh.hasEntries.
Component: Autocomplete → Form Manager
QA Contact: autocomplete → form.manager
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1280945731.1280946733.12595.gz WINNT 5.2 mozilla-central opt test mochitests-5/5 on 2010/08/04 11:15:31 s: win32-slave58 6494 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/components/satchel/test/test_form_submission_cap2.html | Test timed out.
Summary: Intermittent failure in test_form_submission_cap2.html | Test timed ou → Intermittent failure in test_form_submission_cap2.html | Test timed out
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: 13 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.