1526421 - failing test browser_urlbar_search.js when run on windows 10 v1803

Status: RESOLVED FIXED

(Firefox :: Address Bar, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

we are in the process of upgrading our windows10 test machines from v1703 to v1803. In doing so there are a few failures:
browser_urlbar_search.js

here is a try push:
https://treeherder.mozilla.org/#/jobs?repo=try&searchStr=browser-chrome&revision=937618e6864c12a65574d5ead32e4a614a7c957d&selectedJob=226483490

looking at win opt bc3, here is a log:
https://taskcluster-artifacts.net/cTGxJMmyRZeHwhYEJKi1Xg/0/public/logs/live_backing.log

and the related failure messages:
12:16:49 INFO - Buffered messages finished
12:16:49 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_urlbar_search.js | unexpected reflow at _handleOverflow@chrome://global/content/elements/autocomplete-richlistitem.js hit 5 times
12:16:49 INFO - Stack:
12:16:49 INFO - _handleOverflow@chrome://global/content/elements/autocomplete-richlistitem.js:807:20
12:16:49 INFO - _onOverflow@chrome://global/content/elements/autocomplete-richlistitem.js:221:5
12:16:49 INFO - MozAutocompleteRichlistitem/<@chrome://global/content/elements/autocomplete-richlistitem.js:53:45
12:16:49 INFO - EventListener.handleEvent*MozAutocompleteRichlistitem@chrome://global/content/elements/autocomplete-richlistitem.js:53:5
12:16:49 INFO - _appendCurrentResult@chrome://global/content/bindings/autocomplete.xml:1071:22
12:16:49 INFO - _invalidate@chrome://global/content/bindings/autocomplete.xml:916:11
12:16:49 INFO - invalidate@chrome://global/content/bindings/autocomplete.xml:887:11
12:16:49 INFO - testFn/popup.invalidate@chrome://mochitests/content/browser/browser/base/content/test/performance/browser_urlbar_search.js:131:7
12:16:49 INFO - notify@jar:file:///Z:/task_1549452600/build/application/firefox/omni.ja!/components/UnifiedComplete.js:2511:7
12:16:49 INFO - notifyResult@jar:file:///Z:/task_1549452600/build/application/firefox/omni.ja!/components/UnifiedComplete.js:2526:7
12:16:49 INFO - _addMatch@jar:file:///Z:/task_1549452600/build/application/firefox/omni.ja!/components/UnifiedComplete.js:1938:5
12:16:49 INFO - _addFilteredQueryMatch@jar:file:///Z:/task_1549452600/build/application/firefox/omni.ja!/components/UnifiedComplete.js:2244:5
12:16:49 INFO - _onResultRow@jar:file:///Z:/task_1549452600/build/application/firefox/omni.ja!/components/UnifiedComplete.js:1848:9
12:16:49 INFO - handleResult@resource://gre/modules/Sqlite.jsm:785:13
12:16:49 INFO - - false == true - JS frame :: chrome://mochitests/content/browser/browser/base/content/test/performance/head.js :: reportUnexpectedReflows :: line 195

there are many other failures, I suspect the test needs to be adjusted, but maybe this is a browser issue.

Comment 1

[Matthew N. [:MattN]]

Adding [fxperf] since this is a performance test and may indicate performance regressions (or gains).

Comment 2

[Mark Banner (:standard8)]

Has the screen resolution of the new machines been confirmed to be the same as the old ones?

Comparing the screenshot from that builder with the one I just found off a Windows 10 x64 asan builder on mozilla-central - they look different.

New Test builder: https://taskcluster-artifacts.net/cTGxJMmyRZeHwhYEJKi1Xg/0/public/test_info/mozilla-test-fail-screenshot_yq3asg.png
Current m-c: https://taskcluster-artifacts.net/Ce6W15seRuSxgCuFqwAi1g/0/public/test_info/mozilla-test-fail-screenshot_fjqf3o.png

I would expect that a different resolution could easily cause the reflows or layout issues.

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

ok, I had accidentally turned off the mouse and screen resolution script causing this test to fail- re-enabling in bug 1527369