Closed
Bug 634429
Opened 13 years ago
Closed 13 years ago
Test failure in testGetMoreSearchEngines.js | Search engine can not be installed
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aaronmt, Unassigned)
References
()
Details
(Keywords: regression, Whiteboard: [mozmill-test-failure])
Module: testGetMoreSearchEngines.js Test: testGetMoreEngines Error: Search Engine URL contains correct domain - got 'This search engine isn't supported by Namoroka/Shiretoko and can't be installed.', expected 'addons.mozilla.org' Branch: 1.9.2, 1.9.1 Platform: All http://hg.mozilla.org/qa/mozmill-tests/file/535a0763898c/firefox/testSearch/testGetMoreSearchEngines.js#l147 3.6 - http://mozmill-release.brasstacks.mozilla.com/#/general/failure?branch=3.6&platform=All&from=2011-02-08&to=2011-02-12&test=firefox%2FtestSearch%2FtestGetMoreSearchEngines.js&func=testGetMoreEngines 3.5 - http://mozmill-release.brasstacks.mozilla.com/#/general/failure?branch=3.5&platform=All&from=2011-02-09&to=2011-02-13&test=firefox%2FtestSearch%2FtestGetMoreSearchEngines.js&func=testGetMoreEngines
Reporter | ||
Updated•13 years ago
|
Summary: Test failure in testGetMoreSearchEngines | Search engine can not be installed → Test failure in testGetMoreSearchEngines.js | Search engine can not be installed
Updated•13 years ago
|
Comment 1•13 years ago
|
||
Should be working now -- I had to add a ? to the end of the URL to bust cache, initially, but, should just work (tm).
Comment 2•13 years ago
|
||
We will check this in our todays testrun, which gets started around 8am PST. Steven, do you plan to create any test on your side or should we make sure to have at least some tests in Mozmill which operates with the AMO website? I ask because we are moving more and more content to localhost, and things like that wouldn't be caught in the future.
Comment 3•13 years ago
|
||
It's still broken: http://mozmill-release.brasstacks.mozilla.com/#/general/report/cf236ad19b037e87fe0fe25cddfccbef
Comment 4•13 years ago
|
||
Has been fixed last night.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
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
•