Closed Bug 1373879 Opened 7 years ago Closed 7 years ago

Intermittent test_window_rect.py TestSize.test_resize_while_fullscreen | AssertionError: 1280 != 1500

Categories

(Testing :: Marionette Client and Harness, defect)

Version 3
All
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1364319

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

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

Seems to be a Linux only failure. David, could it be a fallout from one of your recent patches?
Flags: needinfo?(dburns)
OS: Unspecified → Linux
Hardware: Unspecified → All
Seeing as this started 2 days ago and my patches around this area have been there for weeks I am suspicious that it is something that I have done.
Flags: needinfo?(dburns)
[task 2017-06-16T22:32:04.479569Z] 22:32:04     INFO - TEST-UNEXPECTED-FAIL | test_window_rect.py TestSize.test_resize_while_fullscreen | AssertionError: 1280 != 1500
[task 2017-06-16T22:32:04.479654Z] 22:32:04     INFO - Traceback (most recent call last):
[task 2017-06-16T22:32:04.479728Z] 22:32:04     INFO -   File "/home/worker/workspace/build/venv/local/lib/python2.7/site-packages/marionette_harness/marionette_test/testcases.py", line 157, in run
[task 2017-06-16T22:32:04.479764Z] 22:32:04     INFO -     testMethod()
[task 2017-06-16T22:32:04.479868Z] 22:32:04     INFO -   File "/home/worker/workspace/build/tests/marionette/tests/testing/marionette/harness/marionette_harness/tests/unit/test_window_rect.py", line 204, in test_resize_while_fullscreen
[task 2017-06-16T22:32:04.479923Z] 22:32:04     INFO -     self.assertEqual(result["width"], self.max["width"] - 100)

So the failure happened in the following line:

> self.assertEqual(result["width"], self.max["width"] - 100)

result is contains the window size after a call to set_window_rect with max-100. So that means the returned value is 1280 which should be the currently available width of the screen. But where does 1500 come from? The only explanation I have here is that using '1500 - 100' as width, results in '1280' as width, which is a difference of 120px.

Is it allowed to resize the window in fullscreen to values larger than the currently available height and width?
Flags: needinfo?(dburns)
We can tell it to resize to anything and then it needs to try do its best.  Seeing as this is resizing to a lot smaller than we are expecting my guess is there is something odd with our linux VM or since we are working with the values that Firefox gives us, something is not reporting correctly. We need to see if there are changes around availHeight/Width or around potential outerHeight/Width APIs.
Flags: needinfo?(dburns)
This could be related to what I see in https://bugzilla.mozilla.org/show_bug.cgi?id=1364319#c27, where I think all WindowProxy references are not being updated correctly.
After having worked extensively on
https://bugzilla.mozilla.org/show_bug.cgi?id=1364319, I’m pretty
confident to say this is a duplicate.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Whiteboard: [stockwell fixed:other]
Product: Testing → Remote Protocol
Moving bug to Testing::Marionette Client and Harness component per bug 1815831.
Component: Marionette → Marionette Client and Harness
Product: Remote Protocol → Testing
You need to log in before you can comment on or make changes to this bug.