Closed
Bug 779926
Opened 12 years ago
Closed 12 years ago
testAddMozSearchProvider failure | Timeout waiting for page loaded
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(firefox14 unaffected, firefox15 affected, firefox16 unaffected, firefox17 unaffected, firefox-esr10 unaffected)
RESOLVED
DUPLICATE
of bug 779488
Tracking | Status | |
---|---|---|
firefox14 | --- | unaffected |
firefox15 | --- | affected |
firefox16 | --- | unaffected |
firefox17 | --- | unaffected |
firefox-esr10 | --- | unaffected |
People
(Reporter: u279076, Unassigned)
References
()
Details
(Whiteboard: [mozmill-test-failure])
/testSearch/testAddMozSearchProvider.js failed in the Firefox 15.0b3 CI testruns on all Windows versions, seems like Mac and Linux were unaffected. There are also no previous instances of this failure on previous Beta builds, nor did it happen with Firefox 16/17 testruns. This could be a one-off connection glitch but I'm filing it anyway. Here is the stack: TimeoutError@resource://mozmill/modules/utils.js:447 waitFor@resource://mozmill/modules/utils.js:485 @resource://mozmill/modules/controller.js:685 @resource://mozmill/modules/controller.js:1328 searchBar_search@resource://mozmill/stdlib/securable-module.js -> file:///c:/docume~1/mozilla/locals~1/temp/tmpytmwzz.mozmill-tests/lib/search.js:813 @resource://mozmill/modules/frame.js -> file:///c:/docume~1/mozilla/locals~1/temp/tmpytmwzz.mozmill-tests/tests/functional/testSearch/testAddMozSearchProvider.js:59 @resource://mozmill/modules/frame.js:591 @resource://mozmill/modules/frame.js:661 @resource://mozmill/modules/frame.js:707 @resource://mozmill/modules/frame.js:540 @resource://mozmill/modules/frame.js:719 @resource://jsbridge/modules/server.js:179 @resource://jsbridge/modules/server.js:183 @resource://jsbridge/modules/server.js:283
status-firefox-esr10:
--- → unaffected
status-firefox14:
--- → unaffected
status-firefox15:
--- → affected
status-firefox16:
--- → unaffected
status-firefox17:
--- → unaffected
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•