Closed
Bug 1326425
Opened 8 years ago
Closed 8 years ago
browser_ext_browserAction_popup_resize.js fails to run on windows 10
Categories
(WebExtensions :: Untriaged, defect, P1)
WebExtensions
Untriaged
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jmaher, Unassigned)
References
Details
(Whiteboard: triaged)
On my local win10 box, I have failures running this test via:
./mach mochitest browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js
this is what I see locally:
254 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js | Document should not be vertically scrollable - Got 49, expected 0
Stack trace:
chrome://mochikit/content/browser-test.js:test_is:913
chrome://mochitests/content/browser/browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js:testPopupSize:228
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
255 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js | Document should not be vertically scrollable - Got 33, expected 0
Stack trace:
chrome://mochikit/content/browser-test.js:test_is:913
chrome://mochitests/content/browser/browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js:testPopupSize:228
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
receiveMessage@resource://testing-common/ContentTask.jsm:113:9
256 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js | Test timed out -
257 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js | Extension left running at test shutdown -
Stack trace:
chrome://mochikit/content/tests/SimpleTest/ExtensionTestUtils.js:ExtensionTestUtils.loadExtension/<:107
chrome://mochikit/content/browser-test.js:Tester.prototype.nextTest<:439
timeoutFn@chrome://mochikit/content/browser-test.js:819:9
setTimeout handler*Tester_execTest@chrome://mochikit/content/browser-test.js:781:9
Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:657:7
SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:744:59
258 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js | Found a browser window after previous test timed out -
259 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/test-oop-extensions/browser_ext_browserAction_popup_resize.js | Document should not be vertically scrollable - Got 49, expected 0
Stack trace:
chrome://mochikit/content/browser-test.js:test_is:913
chrome://mochitests/content/browser/browser/components/extensions/test/browser/test-oop-extensions/browser_ext_browserAction_popup_resize.js:testPopupSize:228
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
260 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/test-oop-extensions/browser_ext_browserAction_popup_resize.js | Document should not be vertically scrollable - Got 33, expected 0
Stack trace:
chrome://mochikit/content/browser-test.js:test_is:913
chrome://mochitests/content/browser/browser/components/extensions/test/browser/test-oop-extensions/browser_ext_browserAction_popup_resize.js:testPopupSize:228
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
TaskImpl_run@resource://gre/modules/Task.jsm:324:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:396:7
TaskImpl_run@resource://gre/modules/Task.jsm:327:15
process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:932:23
walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:813:7
Promise*scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:11
schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:776:7
completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:711:7
receiveMessage@resource://testing-common/ContentTask.jsm:113:9
261 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/test-oop-extensions/browser_ext_browserAction_popup_resize.js | Test timed out -
262 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/test-oop-extensions/browser_ext_browserAction_popup_resize.js | Extension left running at test shutdown -
Stack trace:
chrome://mochikit/content/tests/SimpleTest/ExtensionTestUtils.js:ExtensionTestUtils.loadExtension/<:107
chrome://mochikit/content/browser-test.js:Tester.prototype.nextTest<:439
timeoutFn@chrome://mochikit/content/browser-test.js:819:9
setTimeout handler*Tester_execTest@chrome://mochikit/content/browser-test.js:781:9
Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:657:7
SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:744:59
263 INFO TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/test-oop-extensions/browser_ext_browserAction_popup_resize.js | Found a browser window after previous test timed out -
Buffered messages finished
SUITE-END | took 106s
here is the failure on try:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=e762cd858e7055fdb542480c3ef8734f6f3c5801&filter-tier=1&filter-tier=2&filter-tier=3&selectedJob=65491667&filter-searchStr=tc%20x64%20bc6
note: we are still working on setting up the win10 box on try- so there could be other reasons this fails on try. on debug e10s, it is bc2- not sure why it doesn't fail in non-e10s on try, it fails locally with --disable-e10s.
Comment 1•8 years ago
|
||
The local failure might be a screen size issue. What's the monitor resolution of the machine you tested on?
Reporter | ||
Comment 2•8 years ago
|
||
good point, I have 2560x1440 locally
Comment 3•8 years ago
|
||
Yeah, I think that's too small for that test. I know it fails on my retina MacBook with the same vertical resolution.
I'm looking into why it's failing on infra, though.
Updated•8 years ago
|
Assignee: nobody → kmaglione+bmo
Updated•8 years ago
|
Whiteboard: triaged
Updated•8 years ago
|
Priority: -- → P1
Comment 4•8 years ago
|
||
Is there something here that needs to be done on the infra side to help out?
Comment 5•8 years ago
|
||
If you can make the displayport bigger, that would definitely solve the problem. I don't have another solution other than skipping that test, at this point...
Comment 6•8 years ago
|
||
Or possibly not. I don't remember exactly what error the try builds were failing with, and the logs are gone now...
Comment 7•8 years ago
|
||
It appears that it still might be the case based on a push I found:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=b60be70c69ed7cec2d93b7cd5b847210d1818255&group_state=expanded&filter-searchStr=windows10-64&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=running&filter-resultStatus=pending&filter-resultStatus=runnable&filter-resultStatus=success&selectedJob=89263901
Pete/Rob, is there a way for a test to resize the display port so it has the right resolution needed?
Flags: needinfo?(rthijssen)
Flags: needinfo?(pmoore)
Comment 8•8 years ago
|
||
Hm. The failure screenshot is unusually unhelpful... https://public-artifacts.taskcluster.net/EsEWaPDRTtioYPt0HUG9pg/0/public/test_info/mozilla-test-fail-screenshot_7ezmtc.png
Comment 9•8 years ago
|
||
That is probably related to https://bugzilla.mozilla.org/show_bug.cgi?id=1343580
Depends on: 1343580
Comment 10•8 years ago
|
||
On Windows 10, we currently run as a task user (this behaviour may change to match Windows 7, run as GenericWorker user). Therefore, the desktop resize needs to occur after the task user is created, but before the tests are run. There are two options to achieve this:
- There is a workertype-specific script triggered by generic-worker after creation of task user but before execution of
payload commands which lives in OCC here:
https://github.com/mozilla-releng/OpenCloudConfig/blob/master/userdata/Configuration/GenericWorker/task-user-init-win10.cmd
The script could be extended to include some command that resizes the desktop.
- There are test-specific preflight scripts in-tree. I believe some of these deal with screen size. eg:
https://dxr.mozilla.org/mozilla-central/rev/a374c3546993/testing/mozharness/configs/unittests/win_taskcluster_unittest.py#239
I believe this is the preferred mechanism because of the in-tree transparency for what's happening.
Flags: needinfo?(rthijssen)
Comment 11•8 years ago
|
||
(In reply to Kris Maglione [:kmag] from comment #8)
> Hm. The failure screenshot is unusually unhelpful...
> https://public-artifacts.taskcluster.net/EsEWaPDRTtioYPt0HUG9pg/0/public/
> test_info/mozilla-test-fail-screenshot_7ezmtc.png
The black screen problem was raised in bug 1343580 and will hopefully be solved by the fix proposed in bug 1343582. I'm hoping to get this fixed in the next week.
Flags: needinfo?(pmoore)
Comment 12•8 years ago
|
||
(In reply to Greg Arndt [:garndt] from comment #7)
> Pete/Rob, is there a way for a test to resize the display port so it has the
> right resolution needed?
The current desktop size is successfully set to 1024 x 768 in the tests (the black screenshot https://public-artifacts.taskcluster.net/EsEWaPDRTtioYPt0HUG9pg/0/public/test_info/mozilla-test-fail-screenshot_7ezmtc.png has these dimensions) - however, this desktop is currently not assigned to the win10 process, due to bug 1343582, so perhaps the default display has the wrong size. Hopefully that will fix it when that bug lands, since I believe this is the required desktop size for the tests, and once it is using the correct desktop, I would expect things to start working again, like they do on Windows 7.
Comment 13•8 years ago
|
||
The black screen issue has been solved - see https://bugzilla.mozilla.org/show_bug.cgi?id=1343580#c6 for details.
Comment 14•8 years ago
|
||
Pete, when you have a new try push testing out recent changes, can you let me know so we can check to see if this test is still failing? It appears to be reproducible when the screen resolution is too small so somewhere the screen resolution is not being set to what the test was expecting.
Flags: needinfo?(pmoore)
Reporter | ||
Comment 15•8 years ago
|
||
with the blank screen fixed, I am seeing issues here, a recent screenshot:
https://public-artifacts.taskcluster.net/NCo69-gJQOmYKUIkrF_GHw/0/public/test_info/mozilla-test-fail-screenshot_zbbjsb.png
the log file:
https://public-artifacts.taskcluster.net/NCo69-gJQOmYKUIkrF_GHw/0/public/logs/live_backing.log
and the try push:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=3293c486132d7ba24da29279727bcc3a35c3ea2d&exclusion_profile=false&filter-tier=1&filter-tier=2&filter-tier=3&filter-searchStr=win%20x64%20browser-chrome (between bc2 and bc3)
Flags: needinfo?(pmoore)
Reporter | ||
Comment 16•8 years ago
|
||
in addition there is a devtools test that fails on resize:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=3293c486132d7ba24da29279727bcc3a35c3ea2d&exclusion_profile=false&filter-tier=1&filter-tier=2&filter-tier=3&filter-searchStr=win%20x64%20devtools&selectedJob=100450360
there is only 1 test failure related to devtools:
devtools/client/styleeditor/test/browser_styleeditor_media_sidebar.js
and it fails with:
15:36:01 INFO - 534 INFO TEST-PASS | devtools/client/styleeditor/test/browser_styleeditor_media_sidebar.js | third rule condition text is correct -
15:36:01 INFO - Buffered messages finished
15:36:01 ERROR - 535 INFO TEST-UNEXPECTED-FAIL | devtools/client/styleeditor/test/browser_styleeditor_media_sidebar.js | media rule is now matched after resizing -
15:36:01 INFO - Stack trace:
15:36:01 INFO - chrome://mochitests/content/browser/devtools/client/styleeditor/test/browser_styleeditor_media_sidebar.js:testMediaMatchChanged:78
15:36:01 INFO - chrome://mochitests/content/browser/devtools/client/styleeditor/test/browser_styleeditor_media_sidebar.js:null:49
15:36:01 INFO - Tester_execTest@chrome://mochikit/content/browser-test.js:752:9
15:36:01 INFO - Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:672:7
15:36:01 INFO - SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:795:59
15:36:01 INFO - 536 INFO Leaving test bound
the failing screenshot is:
https://public-artifacts.taskcluster.net/dSJgsJs1QAiN3TpS4sRVnQ/0/public/test_info/mozilla-test-fail-screenshot_prvjen.png
which looks like we don't repaint the window.
So something is odd with window.resize- let me try on a hardware windows-ix machine.
Reporter | ||
Comment 17•8 years ago
|
||
I have verified both browser_ext_browserAction_popup_resize.js and browser_styleeditor_media_sidebar.js work on a windows 10 hardware machine in the datacenter.
A few differences:
* not launched via CI (buildbot or tc), instead launch manually by hand by copying commands from automation
* running win10 build 1703 vs 1607 (shouldn't be a big difference)
* not using open cloud config to make a clean windows 10 environment.
* probably others...
Comment 18•8 years ago
|
||
Thanks Joel for comparing the environments. Definitely looks like something off in the AWS environment, but not quite sure. I looked over the problem with Pete and it seems that the desktop session is setup correctly (the task bar and firefox chrome are drawn correctly).
I am not sure where to start digging in to get better answers of where the problem might be. It really seems like an issue with what Firefox is painting upon resize of the window.
Comment 19•8 years ago
|
||
It's also possible that we're getting the wrong screen geometry in the failing case, for some reason. The resizing code in question tries to never resize the popup so that it extends off-screen, so if it thinks the screen is smaller than it really is, that would prevent the popup from growing.
I can try adding some logs on top of your win10all patch and see if that gets us some more information.
Comment 20•8 years ago
|
||
Looking at the screenshots, somehow firefox seems to have drawn the windows incorrectly - which suggests to me a genuine problem with firefox on Windows 10 with this particular configuration - i.e. if a real world user had the same configuration, I guess the browser would also render like this for them too.
If the screen was completely black, or the browser window didn't open, I could see this as being a worker issue, but the fact that the desktop itself looks normal, and then we have this strangely rendered firefox browser, suggests to me a bug in the browser rendering, rather than the worker environment.
Comment 21•8 years ago
|
||
Unassigning myself, since this seems to be a platform or infra bug. Please let me know if there's anything else I can do.
Assignee: kmaglione+bmo → nobody
Comment 22•8 years ago
|
||
(for my own historical knowledge, this was a mochitest-devtools failure case)
Reporter | ||
Comment 23•8 years ago
|
||
this seems to be working now on more recent try pushes.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•