Open Bug 1600180 Opened 5 years ago Updated 2 years ago

ubuntu1804 - browser/components/sessionstore/test/browser_1446343-windowsize.js | sizemode should match - Got maximized, expected minimized

Categories

(Firefox :: Session Restore, defect, P5)

defect

Tracking

()

REOPENED
Firefox 73
Tracking Status
firefox73 --- affected

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: leave-open)

Attachments

(1 file)

Filed by: egao [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=278675970&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/d2DZl0kuRRWpYZtRheXDVw/runs/0/artifacts/public/logs/live_backing.log


suite: mochitest-browser-chrome
chunk: 4

context:
[task 2019-11-28T21:20:23.665Z] 21:20:23 INFO - TEST-START | browser/components/sessionstore/test/browser_1446343-windowsize.js
[task 2019-11-28T21:20:24.064Z] 21:20:24 INFO - TEST-INFO | started process screentopng
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - TEST-INFO | screentopng: exit 0
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - Buffered messages logged at 21:20:23
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - Entering test bound test
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | width should match on normal mode -
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | height should match on normal mode -
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | screenX should match on normal mode -
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | screenY should match on normal mode -
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | sizemode should match -
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - Buffered messages logged at 21:20:24
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | width should match on maximized mode -
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | height should match on maximized mode -
[task 2019-11-28T21:20:24.461Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | screenX should match on maximized mode -
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | screenY should match on maximized mode -
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | sizemode should match -
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | width should match on minimized mode -
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | height should match on minimized mode -
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | screenX should match on minimized mode -
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - TEST-PASS | browser/components/sessionstore/test/browser_1446343-windowsize.js | screenY should match on minimized mode -
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - Buffered messages finished
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - TEST-UNEXPECTED-FAIL | browser/components/sessionstore/test/browser_1446343-windowsize.js | sizemode should match - Got maximized, expected minimized
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - Stack trace:
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - chrome://mochikit/content/browser-test.js:test_is:1314
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_1446343-windowsize.js:checkCurrentState:26
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_1446343-windowsize.js:test:35
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1069
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1104
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:932
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:805
[task 2019-11-28T21:20:24.466Z] 21:20:24 INFO - Leaving test bound test
[task 2019-11-28T21:20:24.468Z] 21:20:24 INFO - GECKO(8299) | MEMORY STAT | vsize 2856MB | residentFast 361MB | heapAllocated 157MB
[task 2019-11-28T21:20:24.468Z] 21:20:24 INFO - TEST-OK | browser/components/sessionstore/test/browser_1446343-windowsize.js | took 453ms
[task 2019-11-28T21:20:24.469Z] 21:20:24 INFO - checking window state
[task 2019-11-28T21:20:24.469Z] 21:20:24 INFO - GECKO(8299) | must wait for focus
[task 2019-11-28T21:20:24.469Z] 21:20:24 INFO - GECKO(8299) | JavaScript error: resource://specialpowers/SpecialPowersParent.jsm, line 580: TypeError: this.manager.rootFrameLoader is null
[task 2019-11-28T21:20:24.470Z] 21:20:24 INFO - GECKO(8299) | JavaScript error: , line 0: NS_ERROR_UNEXPECTED:
[task 2019-11-28T21:20:24.470Z] 21:20:24 INFO - Console message: [JavaScript Error: "TypeError: this.manager.rootFrameLoader is null" {file: "resource://specialpowers/SpecialPowersParent.jsm" line: 580}]
[task 2019-11-28T21:20:24.471Z] 21:20:24 INFO - Console message: [JavaScript Error: "NS_ERROR_UNEXPECTED: "]

As mentioned in the see also bug chain, my suspicions currently is with the underlying marionette harness, which appears to have issues with the window sizing and placement in ubuntu1804.

See also: 1600391

See Also: → 1600391

I was possibly able to fix this issue by installing compiz on the ubuntu1804 docker image and changing how pulseaudio was initialized in the test-linux.sh script. Putting this bug on hold, and if the changes outlined in the previous sentence do not break anything else, I will close this bug as invalid.

compiz experiment did not work out, so this bug still stands.

Looks like this failure is still reproducible despite changes to marionette driver.js around the resize/repositioning of windows.

:mikedeboer - it would be appreciated if you could redirect the ni to someone that may be able to investigate this permafail on ubuntu1804.

To push to try with ubuntu1804, use ./mach try fuzzy --ubuntu-bionic and select test-linux64 jobs as normal.

Flags: needinfo?(mdeboer)
Assignee: nobody → egao
Attachment #9118107 - Attachment description: Bug 1600180 - makr browser_1446343-windowsize.js as expected failure on ubuntu1804 → Bug 1600180 - mark browser_1446343-windowsize.js as expected failure on ubuntu1804
Status: NEW → ASSIGNED
Pushed by egao@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9900a5f69458
mark browser_1446343-windowsize.js as expected failure on ubuntu1804 r=jmaher
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 73

Reopened and marked as leave-open since this is still an issue - the failure has only been suppressed by marking it skip-if.

The root cause should still be addressed if possible.

Status: RESOLVED → REOPENED
Keywords: leave-open
Resolution: FIXED → ---

This test has been disabled with skip-if in bug 1613983 as part of the linux1804 migration process.

Assignee: egao → nobody
Flags: needinfo?(mdeboer)

Please note that this test has been disabled for all linux1804 platforms and if it is important that this continues to run, please assign a developer to investigate why this test permafails on linux1804. Thanks!

The leave-open keyword is there and there is no activity for 6 months.
:mikedeboer, maybe it's time to close this bug?

Flags: needinfo?(mdeboer)

Note: this happens on Fedora 31 as well, when running tests locally. This may not be specific to that version, or may depend on something like the gnome version

The leave-open keyword is there and there is no activity for 6 months.
:kashav, maybe it's time to close this bug?

Flags: needinfo?(kmadan)

Test is still marked as failing. We'll eventually want to fix it.

Flags: needinfo?(mdeboer)
Flags: needinfo?(kmadan)
Severity: normal normal → S3 S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: