1402089 - browser/base/content/test/performance/browser_startup_images.js (lowdpi) is mostly perma fail on windows10 virtual machines

Status: RESOLVED DUPLICATE of bug 1400357

(Firefox :: General, defect)

Description

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

we have all the browser-chrome tests running in windows 10 on hardware. That is not scalable and we are really close to getting all browser-chrome tests running in a VM (like linux, windows7).

Unfortunately  browser/base/content/test/performance/browser_startup_images.js is failing for us:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=9bd0a7962475ed9b61b5581ba8923013a434f128&selectedJob=132490217

this appears to be an issue in debug primarily, and in the lowdpi ini file.  Here is what we see in the log (https://queue.taskcluster.net/v1/task/bfarLpTNR1OyEkNNCubMcA/runs/0/artifacts/public/logs/live_backing.log ):
5:05:07     INFO -  1 INFO checking window state
15:05:07     INFO -  GECKO(7596) | ++DOCSHELL 00000284C0914800 == 2 [pid = 4524] [id = {80571849-7eba-40d8-bac7-207f54760468}]
15:05:07     INFO -  GECKO(7596) | ++DOMWINDOW == 5 (00000284C091D800) [pid = 4524] [serial = 5] [outer = 0000000000000000]
15:05:07     INFO -  GECKO(7596) | ++DOMWINDOW == 6 (00000284C0A14000) [pid = 4524] [serial = 6] [outer = 00000284C091D800]
15:05:07     INFO -  2 INFO TEST-START | browser/base/content/test/performance/browser_startup_images.js
15:05:07     INFO -  TEST-INFO | started process screenshot
15:05:07     INFO -  TEST-INFO | screenshot: exit 0
15:05:07     INFO -  Buffered messages logged at 15:05:07
15:05:07     INFO -  3 INFO Entering test bound
15:05:07     INFO -  4 INFO TEST-FAIL | browser/base/content/test/performance/browser_startup_images.js | Whitelisted image chrome://global/skin/icons/resizer.png should not have been shown. -
15:05:07     INFO -  5 INFO TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://browser/skin/window-controls/minimize.svg should have been shown. -
15:05:07     INFO -  Buffered messages finished
15:05:07    ERROR -  6 INFO TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://browser/skin/window-controls/maximize.svg should have been shown. -
15:05:07     INFO -  Stack trace:
15:05:07     INFO -  chrome://mochitests/content/browser/browser/base/content/test/performance/browser_startup_images.js:null:106
15:05:07     INFO -  7 INFO TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://browser/skin/window-controls/close.svg should have been shown. -
15:05:07     INFO -  8 INFO TEST-FAIL | browser/base/content/test/performance/browser_startup_images.js | Whitelisted image chrome://browser/skin/tabbrowser/tabDragIndicator.png should not have been shown. -
15:05:07     INFO -  9 INFO TEST-FAIL | browser/base/content/test/performance/browser_startup_images.js | Whitelisted image chrome://browser/skin/arrow-left.svg should not have been shown. -
15:05:07     INFO -  10 INFO TEST-FAIL | browser/base/content/test/performance/browser_startup_images.js | Whitelisted image chrome://browser/skin/tabbrowser/tab-overflow-indicator.png should not have been shown. -
15:05:07     INFO -  11 INFO TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://global/skin/icons/close.svg should have been shown. -
15:05:07     INFO -  12 INFO TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://browser/skin/tabbrowser/newtab.svg should have been shown. -
15:05:07     INFO -  13 INFO TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://global/skin/icons/arrow-dropdown-16.svg should have been shown. -
15:05:07     INFO -  14 INFO TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://browser/skin/back.svg should have been shown. -
15:05:07     INFO -  15 INFO TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://browser/skin/forward.svg should have been shown. -
15:05:07     INFO -  16 INFO TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://browser/skin/reload.svg should have been shown. -
15:05:07     INFO -  17 INFO TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://browser/skin/home.svg should have been shown. -
...


I am not too familiar with this test, I see some intermittent bugs (bug 1378525, and bug 1397055), they don't fail too often though.

Comment 1

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

:johann, would you be able to help me figure out what is going on and figure out a solution.  I am happy to try any hacks here or experiments.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Does that test depend on the screen resolution? Currently we run in 1280x1024 and not 1600x1200 as on the hardware machines:
https://treeherder.mozilla.org/logviewer.html#?job_id=132490217&repo=try&lineNumber=1599

Comment 3

[Johann Hofmann [:johannh]]

This is just bug 1400357, but for lowdpi this time. Now that 57 is merged I can take a look at this tomorrow (it's quite late for me), but if it's really urgent feel free to disable the test on Win 10.

Comment 4

[Johann Hofmann [:johannh]]

(In reply to Johann Hofmann [:johannh] from comment #3)
> This is just bug 1400357, but for lowdpi this time. Now that 57 is merged I
> can take a look at this tomorrow (it's quite late for me), but if it's
> really urgent feel free to disable the test on Win 10.

Take a look == resolve this tomorrow, it's really just a matter of whitelisting maximize.svg.