Closed Bug 672186 Opened 13 years ago Closed 12 years ago

intermittent timeout content/a11y/accessible/editabletext/test_1.html | Test timed out

Categories

(Core :: Disability Access APIs, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mak, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

tinderbox.mozilla.org/showlog.cgi?log=Firefox/1310988680.1310990236.1663.gz

1749 INFO TEST-START | chrome://mochitests/content/a11y/accessible/editabletext/test_1.html
1750 INFO TEST-INFO | chrome://mochitests/content/a11y/accessible/editabletext/test_1.html | before wait for focus -- loaded: loading active window: ([object ChromeWindow]) chrome://browser/content/browser.xul focused window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html desired window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html child window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html docshell visible: true
1751 INFO TEST-INFO | chrome://mochitests/content/a11y/accessible/editabletext/test_1.html | must wait for load
1752 INFO TEST-INFO | chrome://mochitests/content/a11y/accessible/editabletext/test_1.html | already focused
1753 INFO TEST-INFO | chrome://mochitests/content/a11y/accessible/editabletext/test_1.html | maybe run tests <load:false, focus:true> -- loaded: loading active window: ([object ChromeWindow]) chrome://browser/content/browser.xul focused window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html desired window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html child window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html docshell visible: true
1754 INFO TEST-INFO | chrome://mochitests/content/a11y/accessible/editabletext/test_1.html | waitForEvent called <type:load, target[object HTMLDocument]> -- loaded: complete active window: ([object ChromeWindow]) chrome://browser/content/browser.xul focused window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html desired window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html child window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html docshell visible: true
1755 INFO TEST-INFO | chrome://mochitests/content/a11y/accessible/editabletext/test_1.html | maybe run tests <load:true, focus:true> -- loaded: complete active window: ([object ChromeWindow]) chrome://browser/content/browser.xul focused window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html desired window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html child window: ([object Window]) chrome://mochitests/content/a11y/accessible/editabletext/test_1.html docshell visible: true
1756 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/editabletext/test_1.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: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.