Closed
Bug 813449
Opened 12 years ago
Closed 12 years ago
testAwesomeBar/testSuggestHistory.js fails in setupModule() with "Browsing History has been cleared"
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Tracking
(firefox17 fixed, firefox-esr10 fixed, firefox-esr17 fixed)
RESOLVED
FIXED
People
(Reporter: u279076, Unassigned)
References
()
Details
(Whiteboard: [mozmill-test-failure])
Test failed today on Windows XP with the Firefox 17.0build2 candidate. I don't see any instances of this failure in the past week. I was able to find three instances of this failure across all branches and platforms in the last month: http://mozmill-ci.blargon7.com/#/functional/failure?branch=All&platform=All&from=2012-10-19&to=2012-11-20&test=%2FtestAwesomeBar%2FtestSuggestHistory.js&func=testSuggestHistory.js%3A%3AsetupModule
|
||
Updated•12 years ago
|
status-firefox17:
--- → affected
Depends on: 800800
|
||
Comment 1•12 years ago
|
||
Happened yesterday on ESR17 and XP SP3 in the setup module of testCheckItemHighlight.js: http://mozmill-ci.blargon7.com/#/functional/report/352218d7e3125c857fc1d3716707baba
|
|
||
Comment 2•12 years ago
|
||
Happened today on XP SP3 with ESR10 in testEscapeAutocomplete - setupModule http://mozmill-ci.blargon7.com/#/functional/report/352218d7e3125c857fc1d3716723c2e5
|
|
||
Comment 3•12 years ago
|
||
Happened on XP SP3 with ESR 17 en_US - setupModule http://mozmill-ci.blargon7.com/#/functional/report/352218d7e3125c857fc1d3716725ac8e Happened on XP SP3 with FF 17.0.1 en_US http://mozmill-ci.blargon7.com/#/functional/report/352218d7e3125c857fc1d37167280613
status-firefox-esr10:
--- → affected
status-firefox-esr17:
--- → affected
|
||
Comment 4•12 years ago
|
||
One more failure today on XP SP 3 with 17.0.1pre http://mozmill-ci.blargon7.com/#/functional/report/352218d7e3125c857fc1d3716787ee5f
|
||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 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
•