Fission + sw-wr: TEST-UNEXPECTED-TIMEOUT | /webdriver/tests/minimize_window/minimize.py | expected OK
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: cpeterson, Unassigned)
References
(Blocks 1 open bug)
Details
In bug 1697195, we tried to auto-enable SW-WR with Fission is enabled. Unfortunately, some tests failed when run with Fission + SW-WR mode:
webdriver failures:
https://treeherder.mozilla.org/logviewer?job_id=332583137&repo=autoland&lineNumber=70490
TEST-UNEXPECTED-TIMEOUT | /webdriver/tests/minimize_window/minimize.py | expected OK
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
Sending this bug to gfx-triage.
Does this webdriver test time out when is SW-WR enabled without Fission? This seems like a SW-WR bug.
Reporter | ||
Comment 3•4 years ago
|
||
Tracking for Fission M7a Beta. TBD whether SW-WR will block Fission MVP.
Comment 4•4 years ago
|
||
I can't reproduce this on macOS. Treeherder seems to say it has only been sighted on Windows. I'll take myself off needinfo and we'll discuss it again in triage.
![]() |
||
Comment 5•4 years ago
•
|
||
Using the following on Windows -
mach wpt testing/web-platform/tests/webdriver/tests/minimize_window/minimize.py --enable-fission --setpref="gfx.webrender.software=true"
I can't reproduce. I want to confirm I'm actually getting the config I'm requesting.
Chris, what config are we testing in 'opt-web-platform-tests-wdspec-fis-e10s-1'? Does that e10s-1 imply some sort of single content process test environment?
![]() |
||
Comment 6•4 years ago
|
||
also tried -
mach wpt testing/web-platform/tests/webdriver/tests/minimize_window/minimize.py --enable-fission --setpref="gfx.webrender.software=true" --setpref="gfx.webrender.software.d3d11=false"
![]() |
||
Comment 7•4 years ago
|
||
Interesting that this test fails when marionette is trying to make the window fullscreen, and gives the browser 5 seconds to complete the operation. This makes me think it's some sort of timeout related to slow painting. Definitely doesn't reproduce on my beefy workstation.
Reporter | ||
Comment 8•4 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #5)
Chris, what config are we testing in 'opt-web-platform-tests-wdspec-fis-e10s-1'? Does that e10s-1 imply some sort of single content process test environment?
The "e10s-1" just means this test is running with content processes (not the pre-e10s "1proc") and is in the first batch of tests. Tests with many sub-test cases are automatically split into small batches to reduce timeouts.
So test-windows10-64-qr/opt-web-platform-tests-wdspec-fis-e10s-1
is opt Windows build running on 64-bit Windows 10 with WebRender ("qr") and Fission ("fis") enabled.
![]() |
||
Comment 9•4 years ago
|
||
Currently not having any luck reproducing this failure on try - https://treeherder.mozilla.org/jobs?repo=try&revision=20f6177b9dec25b04df8ec6d513e3660b04b4f07&selectedTaskRun=FUhQEVHZQ0SxyGUcypXU1g.0
![]() |
||
Updated•4 years ago
|
![]() |
||
Updated•4 years ago
|
Description
•