Closed Bug 1402610 Opened 7 years ago Closed 7 years ago

Permaorange Windows 10 browser/base/content/test/performance/browser_windowopen_reflows.js | unexpected uninterruptible reflow

Categories

(Firefox :: General, defect)

x86_64
Windows 10
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1402079
Tracking Status
firefox58 --- affected

People

(Reporter: philor, Unassigned)

References

Details

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

Boring backstory: we still run browser-chrome on buildbot Windows 10 hardware, though we're trying to move it to taskcluster VMs. One of the problems with the VMs is that we were running them at 1024x768 resolution, which is too short for a fair number of suites. But they don't want to run at the 1600x1200 we run on hardware, so bug 1401501 moved both the VMs and the hardware to run at 1280x1024. Everything was green.

When something in https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=8c3a1558322331c1fab9d1d2d7a94ef69f2a9212 from autoland met up with https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=8db0c4ecd94cb62a35a25a5fe411d9f0aed7087e which merged the resolution change from inbound, we got two things: perhaps related and perhaps unrelated, the line of plain text and links that's browser/base/content/test/general/browser_bug970746.xhtml started laying out just differently enough that it put a line break in the wrong place and made bug 1402070 permaorange, and it gave us permaorange

https://treeherder.mozilla.org/logviewer.html#?job_id=132836821&repo=mozilla-central

03:40:15     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_windowopen_reflows.js | unexpected uninterruptible reflow 
03:40:15     INFO - [
03:40:15     INFO - 	"handleEvent@chrome://browser/content/tabbrowser.xml:6863:19",
03:40:15     INFO - 	"select@chrome://global/content/bindings/textbox.xml:115:11",
03:40:15     INFO - 	"focusAndSelectUrlBar@chrome://browser/content/browser.js:2290:5",
03:40:15     INFO - 	"_setInitialFocus/<@chrome://browser/content/browser.js:1632:11",
03:40:15     INFO - 	"promise callback*_setInitialFocus@chrome://browser/content/browser.js:1630:5",
03:40:15     INFO - 	"onLoad@chrome://browser/content/browser.js:1400:5",
03:40:15     INFO - 	"onload@chrome://browser/content/browser.xul:1:1",
03:40:15     INFO - 	""
03:40:15     INFO - ]
03:40:15     INFO -  - false == true - JS frame :: chrome://mochitests/content/browser/browser/base/content/test/performance/head.js :: reflow :: line 122
03:40:15     INFO - Stack trace:
03:40:15     INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:reflow:122
03:40:15     INFO - chrome://browser/content/tabbrowser.xml:handleEvent:6863
03:40:15     INFO - chrome://global/content/bindings/textbox.xml:select:115
03:40:15     INFO - chrome://browser/content/browser.js:focusAndSelectUrlBar:2290
03:40:15     INFO - chrome://browser/content/browser.js:_setInitialFocus/<:1632
fixed in bug 1402079
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Whiteboard: [stockwell fixed:other]
You need to log in before you can comment on or make changes to this bug.