Closed
Bug 760376
Opened 12 years ago
Closed 12 years ago
Failure in testSearch::testGetMoreSearchEngines.js | Modal dialog has been found
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(firefox12 unaffected, firefox13 unaffected, firefox14 wontfix, firefox15 wontfix, firefox18 affected, firefox19 affected, firefox20 affected, firefox21 affected, firefox-esr10 wontfix)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox12 | --- | unaffected |
firefox13 | --- | unaffected |
firefox14 | --- | wontfix |
firefox15 | --- | wontfix |
firefox18 | --- | affected |
firefox19 | --- | affected |
firefox20 | --- | affected |
firefox21 | --- | affected |
firefox-esr10 | --- | wontfix |
People
(Reporter: u279076, Unassigned)
References
()
Details
(Whiteboard: [mozmill-test-failure])
Not sure if this is related to bug 749159 or not, but testGetMoreSearchEngines.js failed today with "Modal dialog has been found and processed". This was with the ondemand testrun with 10.0.5esr candidate builds. Only one instance was captured on Mac OSX 10.7. http://mozmill-ondemand.blargon7.com/#/functional/report/fdec829b93b19c73985be1d38840ebac
Comment 1•12 years ago
|
||
There are different behaviors here. Sometimes we run into a timeout loading the page. Those are the most common failures in the last days. See the test results.
Updated•12 years ago
|
status-firefox-esr10:
--- → affected
status-firefox12:
--- → unaffected
status-firefox13:
--- → unaffected
status-firefox14:
--- → affected
status-firefox15:
--- → affected
Comment 2•12 years ago
|
||
No more test failures since end of May. Lets close this bug as WFM for the time being. We will reopen if the failure comes back.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•11 years ago
|
status-firefox18:
--- → affected
status-firefox19:
--- → affected
status-firefox20:
--- → affected
status-firefox21:
--- → affected
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
•