| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| workarounds/tests-Mark-view-verification-tests-as-incomplete-in-big-e.patch | tests: Mark view-verification tests as incomplete in big-endian archs Saved pixmaps are invalid in big-endian architectures, so let's disable the tests for now, checking only the basic metadata but not comparing the contents. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | yes | upstream | 2021-06-15 | |
| debian/tests-Do-not-run-screencast-tests.patch | tests: Do not run screencast tests They require to have a full running pipewire (that requires a system dbus daemon) so, we can't easily get one up and running while building. So let's disable this for now |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2021-05-20 | ||
| debian/Support-Dynamic-triple-double-buffering.patch | Support Dynamic triple/double buffering Use triple buffering if and when the previous frame is running late. This means the next frame will be dispatched on time instead of also starting late. It also triggers a GPU clock boost if deemed necessary by the driver. Although frequency scaling is not required to get a performance gain here because even a fixed frequency GPU will benefit from not over-sleeping anymore. If the previous frame is not running late then we stick to double buffering so there's no latency penalty when the system is able to maintain full frame rate. Formatted for Debian (as of 47) with: git remote add community-ubuntu git@ssh.gitlab.gnome.org:Community/Ubuntu/mutter.git git fetch community-ubuntu git merge --squash -e community-ubuntu/triple-buffering-v4-47 And then git commit but using all this as the header instead of what git suggests. Also add Gbp-Pq: Topic debian |
Daniel van Vugt <daniel.van.vugt@canonical.com> | yes | upstream | 2024-10-31 | |
| workarounds/tests-skip-monitor-width-size-check-as-it-may-lead-to-une.patch | tests: skip monitor width size check as it may lead to unexpected failure This seems to be broken only on autopkg-tests. |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | not-needed | 2022-03-14 | ||
| workarounds/tests-Skip-thread-priority-test.patch | tests: Skip thread priority test This test added to 45 fails on Ubuntu's armhf builders https://launchpad.net/ubuntu/+source/mutter/45~beta.1-0ubuntu1/+latestbuild/armhf and on Debian's i386 https://buildd.debian.org/status/logs.php?pkg=mutter&arch=i386 Architecture defines are at https://wiki.debian.org/ArchitectureSpecificsMemo |
=?utf-8?q?Jeremy_B=C3=ADcha?= <jeremy.bicha@canonical.com> | no | 2023-08-21 | ||
| workarounds/place-Always-center-initial-setup.patch | place: Always center initial-setup | =?utf-8?q?Florian_M=C3=BCllner?= <fmuellner@gnome.org> | not-needed | https://src.fedoraproject.org/rpms/mutter/blob/main/f/0001-place-Always-center-initial-setup-fedora-welcome.patch | 2022-12-02 | |
| workarounds/Mark-several-additional-tests-as-flaky.patch | Mark several additional tests as flaky Most of these have never been reliable on Debian buildds, especially on ARM, so having them fail is not a regression. They usually succeed after a few retries, but that's time-consuming and unsuitable to be a QA gate. The input-capture test frequently hangs until it times out, so put that one in a separate suite so that we don't need to run it at all. |
Simon McVittie <smcv@debian.org> | no | 2023-12-13 | ||
| workarounds/tests-Install-stacking-tests-into-a-subdirectory.patch | tests: Install stacking tests into a subdirectory These are not reliable enough on ci.debian.net to be used as a QA gate. |
Simon McVittie <smcv@debian.org> | not-needed | debian | 2024-09-07 |