Closed Bug 807251 Opened 13 years ago Closed 12 years ago

Test failure "Suggestions are different - got 'false'" in testSearch/testSearchSuggestions.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P3)

defect

Tracking

(firefox19 fixed, firefox20 fixed, firefox21 fixed, firefox22 fixed, firefox-esr17 fixed)

RESOLVED FIXED
Tracking Status
firefox19 --- fixed
firefox20 --- fixed
firefox21 --- fixed
firefox22 --- fixed
firefox-esr17 --- fixed

People

(Reporter: AndreeaMatei, Assigned: daniela.p98911)

References

()

Details

(Whiteboard: [mozmill-test-failure] s=130204 u=failure c=search p=1)

Attachments

(1 file, 1 obsolete file)

Happens on Windows for now, with Aurora build. This fails at the last check from the test.
Whiteboard: [mozmill-test-failure]
Looks like this might have been a one-off. It occurred a few times in July/August on ESR. We could try to replicate it under heavy load, or add some debug statements for the next time it fails.
Priority: -- → P3
Didn't happen again.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
It happened last night: http://mozmill-ci.blargon7.com/#/functional/report/9e41582ed5e806fa373351d9d32035f1 It's extremely rare, we weren't able to reproduce it. The cause must be that the suggestions are not being populated and Daniela found bug 542990 where this is a known issue, just it didn't got fixed.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
We should improve the checks so we know what we are comparing too. Lets take it for next week.
Status: REOPENED → NEW
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure] s=130204 u=failure c=search p=1
Assignee: nobody → dpetrovici
Status: NEW → ASSIGNED
Attached patch patch v1.0 (improve checks) (obsolete) — Splinter Review
This is only to improve the check for suggestions per previous comment
Attachment #710159 - Flags: review?(andreea.matei)
Comment on attachment 710159 [details] [diff] [review] patch v1.0 (improve checks) Review of attachment 710159 [details] [diff] [review]: ----------------------------------------------------------------- This will do for debug, but I still feel is not enough. We should also see the exact suggestion/s that caused the test to fail, maybe is always the same. Instead of using dumps, could we make use of throws recently added?
Attachment #710159 - Flags: review?(andreea.matei) → review-
Changed the error message to show the suggestions for one search provider. In case assert.ok fails, then all suggestions for the two search providers are the same.
Attachment #710159 - Attachment is obsolete: true
Attachment #710704 - Flags: review?(andreea.matei)
Comment on attachment 710704 [details] [diff] [review] patch v1.1 (improve checks) Review of attachment 710704 [details] [diff] [review]: ----------------------------------------------------------------- Great, this allows us to get the suggestions as well as the providers next time we're failing.
Attachment #710704 - Flags: review?(andreea.matei) → review+
Keywords: checkin-needed
Comment on attachment 710704 [details] [diff] [review] patch v1.1 (improve checks) Review of attachment 710704 [details] [diff] [review]: ----------------------------------------------------------------- http://hg.mozilla.org/qa/mozmill-tests/rev/945cbb978d10 (default)
Attachment #710704 - Flags: checkin+
This patch applies clearly on all branches
The issue did not reproduce in a month (since 01/30).
Lets reopen if needed.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Anthony, this is an old fixed bug. Please create a new one with the specific locales in question in the summary. That way we can differentiate it. Thanks.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
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: