Closed Bug 701901 Opened 13 years ago Closed 12 years ago

Failure in testSearch::testGetMoreSearchEngines.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

defect
Not set
normal

Tracking

(firefox12 fixed, firefox13 fixed, firefox14 fixed, firefox15 fixed, firefox-esr10 fixed)

RESOLVED FIXED
Tracking Status
firefox12 --- fixed
firefox13 --- fixed
firefox14 --- fixed
firefox15 --- fixed
firefox-esr10 --- fixed

People

(Reporter: u279076, Assigned: remus.pop)

References

()

Details

(Whiteboard: [mozmill-test-failure][qa-])

Attachments

(2 files, 1 obsolete file)

MODULE: tests/functional/testSearch/testGetMoreSearchEngines.js
TEST: testGetMoreEngines
FAIL: TimeoutError("Modal dialog has been found and processed")@resource://mozmill/modules/utils.js:429 waitFor([object Proxy],"Modal dialog has been found and processed",30000,100,[object Proxy])@resource://mozmill/modules/utils.js:467 
BRANCH: mozilla-release, mozilla-beta, mozilla-aurora, default
Assignee: nobody → remus.pop
The only fail closer to this is the waitForPageLoad error. I cannot reproduce the other one.
Anyway the cause for this would likely be no response from the network when we click the Add to Firefox button. If this would be the case, the solution lies in installing a search engine from localhost.
Any other info would be appreciated.
This should be tested on qa-horus if it can't be reproduced locally. Does it happen all the time? Only for the daily testrun or also when the test module or the folder gets executed? Which platforms are affected? This information I kinda miss in the initial comments all over the place now. :/
Last week (11th to 18th of November) only one fail occured for this test: 
* controller.waitForPageLoad(): Timeout waiting for page loaded
which I mentioned earlier.
I'm only seeing 2 instances of this failure in the last week. Once on 10.0a2 and another time with 8.0.1. I'm thinking this is most likely due to a connectivity glitch.

Resolving WONTFIX for now. We can reopen if this starts happening much more frequently.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Reopening this due to failure in the 9.0b5 testruns today:
http://mozmill-release.brasstacks.mozilla.com/#/functional/report/e6d78e062edb343a967207c43d2b8595

This only happened once and given the history of this bug I think it's safe to say this is a very intermittent failure.

Remus, please submit a patch to disable this test immediately. It is unreliable in it's current form and will likely need to be refactored.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Attached patch patch v1.0 (obsolete) — Splinter Review
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #5)
> Remus, please submit a patch to disable this test immediately. It is
> unreliable in it's current form and will likely need to be refactored.
Remus had some work with other tests. Seeing as this was marked as "immediately", I took the liberty of skipping it. Hope it's ok.
Assignee: remus.pop → alex.lakatos
Attachment #580054 - Flags: review?(anthony.s.hughes)
Attachment #580054 - Flags: review?(anthony.s.hughes) → review+
Your commit message is backwards -- please use the correct format. I've uploaded a corrected patch.
Attachment #580054 - Attachment is obsolete: true
Attachment #580096 - Flags: review+
Status: REOPENED → ASSIGNED
Summary: Failure in testGetMoreSearchEngines.js: Modal dialog has been found and processed → Failure in testSearch::testGetMoreSearchEngines.js
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][mozmill-test-skipped]
Comment on attachment 580096 [details] [diff] [review]
disable test (default/aurora/beta) [checked-in]

Landed:
http://hg.mozilla.org/qa/mozmill-tests/rev/18fcf9ce8996 (default)
http://hg.mozilla.org/qa/mozmill-tests/rev/a5d218c82cab (mozilla-aurora)
http://hg.mozilla.org/qa/mozmill-tests/rev/e8048efe8d39 (mozilla-beta)
Attachment #580096 - Attachment description: disable test (default/aurora/beta) → disable test (default/aurora/beta) [checked-in]
This enables the test.
Attachment #625048 - Flags: review?(dave.hunt)
Remus: Could you resubmit results for Linux? The test is skipped in the report you've linked to in comment 9. Once I've seen that it's passing I can r+ this and land it.
Assignee: alex.lakatos → remus.pop
It seems I may forgot to qrefresh before the testrun. So here are the new results. testGetMoreSearchEngines is included.
Thanks Remus. Landed as:
http://hg.mozilla.org/qa/mozmill-tests/rev/01dbffb740b4

Once we have this passing we can transplant it to the remaining branches.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago12 years ago
Resolution: --- → FIXED
Yay! So lets now get the appropriate Litmus tests updated (if necessary).
Flags: in-litmus?(remus.pop)
Whiteboard: [mozmill-test-failure][mozmill-test-skipped] → [mozmill-test-failure]
Dave: wrote it down.

Here are the links from Litmus for this test:

Release:
https://litmus.mozilla.org/show_test.cgi?id=50825

Beta:
https://litmus.mozilla.org/show_test.cgi?id=55695

Aurora:
https://litmus.mozilla.org/show_test.cgi?id=15702
Flags: in-litmus?(remus.pop) → in-litmus+
This also needs an update of the 10.0 Litmus test.
Flags: in-litmus+ → in-litmus?(remus.pop)
Missed it. 
Firefox ESR (10.0):
https://litmus.mozilla.org/show_test.cgi?id=40800
Flags: in-litmus?(remus.pop) → in-litmus+
Comment on attachment 625048 [details] [diff] [review]
enable test v1 (all branches) [checked-in]

Missed setting the r+ when I landed this.
Attachment #625048 - Flags: review?(dave.hunt) → review+
Attachment #625048 - Attachment description: enable test v1 (all branches) → enable test v1 (all branches) [checked-in]
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][qa-]
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: