Perma gfx/layers/apz/test/mochitest/mochitest.ini failures on new Ubuntu 22.04 Wayland pool
Categories
(Core :: Panning and Zooming, defect, P3)
Tracking
()
People
(Reporter: ahal, Unassigned)
References
Details
This is happening on a new Ubuntu 22.04 Wayland enabled pool we're in the process of standing up.
Example failure log:
https://treeherder.mozilla.org/logviewer?job_id=431033471&repo=try&lineNumber=12148
There are many tests affected here, they seem related to wheel events:
- test_bug1253683.html
- test_bug1277814.html
- test_group_hittest-2.html
- test_group_mouseevents.html
- test_group_overrides.html
- test_group_overscroll.html
- test_group_overscroll_handoff.html
- test_group_scroll_snap.html
- test_group_scrollend.html
- test_group_scrollframe_activation.html
Some of them appear to be intermittent, while others are permafail (or just very frequent intermittent).
It's unclear whether these are a result of Wayland, upgrading to Ubuntu 22.04 or hardware characteristics of the new workers. The tests will be skipped on this new platform.
|
||
Comment 2•2 years ago
|
||
(In reply to Hiroyuki Ikezoe (:hiro) from comment #1)
This is due to the wayland backend.
Razvan ran into this while trying to run APZ mochitests locally on Wayland, and found an open feature request for the needed Wayland API to be added: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158
|
||
Comment 3•2 years ago
|
||
Could all those problems with events here be related to issues with retrieving the correct timestamp? I've found bug 1861933 which drastically causes intermittent failures for our remote browser-chrome tests. More or less often a timestamp previously taken is larger than the current one. I assume that this could have an effect on events.
|
||
Comment 4•2 years ago
|
||
I don't think so. There may be some test cases related the timestamp issue but I doubt it because these failures are perma, not imtermittent.
|
|
||
Comment 5•2 years ago
|
||
My understanding is we already have a diagnosis for the perma-failure of the tests listed in this bug: they try to synthesize native mouse move events and Wayland doesn't currently support that.
|
|
||
Comment 6•1 year ago
|
||
(In reply to Botond Ballo [:botond] from comment #2)
(In reply to Hiroyuki Ikezoe (:hiro) from comment #1)
This is due to the wayland backend.
Razvan ran into this while trying to run APZ mochitests locally on Wayland, and found an open feature request for the needed Wayland API to be added: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158
Update: this Wayland feature has now been implemented.
Description
•