Closed
Bug 1491971
Opened 7 years ago
Closed 2 years ago
Hangs in "WebDriver:FullscreenWindow"
Categories
(Remote Protocol :: Marionette, defect, P3)
Tracking
(firefox65 affected)
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox65 | --- | affected |
People
(Reporter: whimboo, Unassigned)
References
Details
(Keywords: hang)
Similar to bug 1489955 the "WebDriver:FullscreenWindow" command hangs and doesn't return. As result Firefox gets killed after reaching the timeout.
This is actually a permafail for wpt.fyi test results, and marks all the tests in `set.py` as missing:
https://staging.wpt.fyi/results/webdriver/tests/set_window_rect/set.py?sha=d36d9f4077
Here the log file from Taskcluster:
https://taskcluster-artifacts.net/ANhqpIf7TfWvXpyS3lk9XA/0/public/logs/live_backing.log
> 28:55.63 .. 1537208827023 Marionette TRACE 0 -> [0,945,"WebDriver:FullscreenWindow",{}]
> 31:54.48 .. TEST_END: TIMEOUT, expected OK
Andreas, given that you worked on the fullscreen / set window rect implementation for Marionette, and the failure seems to be very specific to Linux, can you please work on that bug?
If we cannot find the underlying issue I would even be happy with using the TimedPromise for waiting of the expected events. That way we could at least return a failure after eg. 15s, and don't hang forever.
We should treat this failure with high priority.
Flags: needinfo?(ato)
| Reporter | ||
Comment 1•7 years ago
|
||
Please note that when you check the above TaskCluster log file all window tests which call `WebDriver:Fullscreen` hang. So this affects the fullscreen, maximize, minimize, and set window rect commands.
Comment 2•7 years ago
|
||
I can’t work on this right now, but can take a look once I’ve
finished my P1s and my other P2s.
Flags: needinfo?(ato)
Updated•7 years ago
|
Assignee: nobody → ato
Comment 3•7 years ago
|
||
Setting this to P3 as it's only wpt.fyi. If it moves to our CI then we can revisit
Priority: P2 → P3
Comment 4•7 years ago
|
||
There are some fundamental restrictions we can’t get with window
manipulation. If you run Firefox in Xvfb without a window manager,
it will not be possible to put the browser into fullscreen mode.
To make the matter worse, we also cannot detect if the browser is
run inside a capable WM. Our only option in this case is to fall
back to a timeout, hoping the browser has reached its dimensions
but the window state will likely not reach "fullscreen".
Comment 5•7 years ago
|
||
This should be solved with https://bugzilla.mozilla.org/show_bug.cgi?id=1492499.
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 6•7 years ago
|
||
No timeout anymore for wpt.fyi fullscreen tests. Thanks a lot!
https://wpt.fyi/results/webdriver/tests/fullscreen_window?label=experimental
status-firefox65:
--- → fixed
Target Milestone: --- → mozilla65
| Reporter | ||
Comment 7•7 years ago
|
||
This is not completely fixed. Bug 1508101 was raised recently.
Assignee: ato → nobody
Blocks: 1508101
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: mozilla65 → ---
Updated•3 years ago
|
Severity: critical → S2
Updated•3 years ago
|
Product: Testing → Remote Protocol
| Reporter | ||
Comment 8•2 years ago
|
||
We haven't seen hangs for this command for quite some time. As such lets close this bug.
Status: REOPENED → RESOLVED
Closed: 7 years ago → 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•