Closed Bug 1406860 Opened 8 years ago Closed 8 years ago

Intermittent browser/base/content/test/urlbar/browser_autocomplete_tag_star_visibility.js | Result should have expected type - Got (tag|favicon), expected bookmark

Categories

(Toolkit :: Places, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla58
Tracking Status
firefox58 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: mak)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell fixed:other])

Attachments

(1 file)

Some of the tests in urlbar/ are intermittent-prone, they check richlistbox children existence, but they don't wait for the child to be up-to-date. Among these: browser_urlbar_search_no_speculative_connect_with_client_cert.js browser_autocomplete_tag_star_visibility.js browser_autocomplete_no_title.js And most of the tests using gURLBar.popup.richlistbox.children: http://searchfox.org/mozilla-central/search?q=gURLBar.popup.richlistbox.children&path=urlbar%2F
Assignee: nobody → mak77
Status: NEW → ASSIGNED
Priority: P5 → P1
I'll still fix these tests, because sooner or later they'll bite us.
the only test failure I could still reproduce on Try is browser_urlbarSearchSuggestions_opt-out.js. That test is expected to click on the location bar and the notification should appear. Sometimes on Linux the click goes through, the locationbar is focused, but still the popup doesn't show. But that failure is already tracked in bug 1397154, so we can handle it apart, provided we understand what's up. Or we could disable it on Linux.
Summary: Intermittent browser/base/content/test/urlbar/browser_autocomplete_tag_star_visibility.js | Result should have expected type - Got tag, expected bookmark → Intermittent browser/base/content/test/urlbar/browser_autocomplete_tag_star_visibility.js | Result should have expected type - Got (tag|favicon), expected bookmark
Comment on attachment 8917159 [details] Bug 1406860 - Make urlbar tests a bit more reliable. https://reviewboard.mozilla.org/r/188180/#review193546 Looks good, lets try it :-) ::: browser/base/content/test/urlbar/browser_action_searchengine.js:13 (Diff revision 1) > let originalEngine = Services.search.currentEngine; > Services.search.currentEngine = engine; > > let tab = await BrowserTestUtils.openNewForegroundTab(gBrowser, "about:mozilla"); > > - registerCleanupFunction(() => { > + registerCleanupFunction(async function() { Why not `async () => {`? ::: browser/base/content/test/urlbar/browser_action_searchengine_alias.js:14 (Diff revision 1) > let originalEngine = Services.search.currentEngine; > Services.search.currentEngine = engine; > > let tab = await BrowserTestUtils.openNewForegroundTab(gBrowser, "about:mozilla"); > > - registerCleanupFunction(() => { > + registerCleanupFunction(async function() { ditto.
Attachment #8917159 - Flags: review?(standard8) → review+
thanks for picking this bug up so quickly and getting a fix in place
Whiteboard: [stockwell needswork]
(In reply to Mark Banner (:standard8) from comment #8) > Why not `async () => {`? I probably didn't really mean to change that. In general I think arrow functions are a bit less optimized and more expensive because they have to bind "this". So, I usually tend to avoid them unless it's a very short callback (readability win) or I need the bind. In practice it doesn't really matter. I'll revert those changes for the sake of preserving blame.
oh wait, I wouldn't really preserve any blame here, cause the previous arrow function was not async. I'l leave the patch as-is, since arrow functions are not really needed here.
Pushed by mak77@bonardo.net: https://hg.mozilla.org/integration/autoland/rev/1ac7fce0b369 Make urlbar tests a bit more reliable. r=standard8
Backed out for failing xpcshell tests, e.g. toolkit/components/places/tests/unit/test_000_frecency.js: https://hg.mozilla.org/integration/autoland/rev/f1fb2969c2b3f1f4a0f8a4be8dbe06fd0b6ec01f Push with failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=1ac7fce0b369889c60010e66085d2bf0eb8bc250&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=runnable Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=136229951&repo=autoland TEST-UNEXPECTED-FAIL | toolkit/components/places/tests/unit/test_000_frecency.js | xpcshell return code: 0 TEST-UNEXPECTED-FAIL | toolkit/components/places/tests/unit/test_463863.js | xpcshell return code: 0 TEST-UNEXPECTED-FAIL | toolkit/components/places/tests/unit/test_multi_queries.js | xpcshell return code: 0
Flags: needinfo?(mak77)
my fault, I forgot that EMBED visits are not returned by history.fetch. It's a simple fix.
Flags: needinfo?(mak77)
Pushed by mak77@bonardo.net: https://hg.mozilla.org/integration/autoland/rev/c2bb5a120db9 Make urlbar tests a bit more reliable. r=standard8
See Also: → 1407827
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla58
Blocks: 1407129
Blocks: 1407235
Blocks: 1407133
Blocks: 1382610
Blocks: 1354681
Whiteboard: [stockwell needswork] → [stockwell fixed:other]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: