Closed p-gentili closed 2 months ago
Attention: Patch coverage is 95.42857%
with 8 lines
in your changes missing coverage. Please review.
Project coverage is 44.27%. Comparing base (
76939c4
) to head (3ea1eae
). Report is 30 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
A few changes below, but I've tried both this and the "original" script on my machine and it doesn't seem to work with i3 (unsurprisingly, as it doesn't use Mutter). My question is, how limiting is this? We do use Checkbox on non-mutter platforms as well (like Mir for example). Could this be a problem? Is it possible to somehow calculate the
OBJECT_PATH
,NAME
andINTERFACE
to "fix" this?
With the current implementation, relying on xrandr and gnome-randr, we are covering everything X11 + Gnome Wayland. With the latest few commits I re-included support for X11 via xrandr
so that the coverage is the same. I still prefer to use Mutter over xrandr on Gnome because I feel like it should handle corner cases better (let me know if you're against this choice). We'll need to add support for other Wayland compositors, such as Mir or wlroots-based.
Got part of the xrandr
parser from https://github.com/canonical/checkbox/pull/1229 and added support for setting a new display configuration, in extended mode.
Both handlers inherit from the same abstract class so that the interface is the same and the EDID test itself doesn't care about the actual system.
Tested on:
Description
The Zapper EDID cycling job is failing on laptops because Mirror mode is making the external monitor match the internal display resolution. Like this:
gnome-randr
can't be used for applying monitor configurations, and in general having two utilities (xrandr and gnome-randr) for x11 and wayland doesn't help with maintainability of this test.This PR relies on DBus and Mutter to retrieve the current monitor configuration and apply extended mode every time we switch EDID.
Resolved issues
Resolves ZAP-677
Documentation
Up to date
Tests
Tested on 202302-31240
side-loading the providerrunning from source. Previously failing like above (ref).