https://buildd.debian.org/status/logs.php?pkg=mutter&arch=armhf

There is no clear pattern why/how it fails, but builds are
supposed to be non-flaky.

Control: found -1 49.4-1
Control: tags -1 + help

This is not a new problem, so I'm marking it as found in testing to
avoid it blocking migration. #1121518 is essentially the same thing.

Anyone who can help to debug/improve the tests is more than welcome to
do so, especially the porting teams for the affected architectures (I
don't think anyone in the GNOME team is running it on armhf).
Unfortunately upstream only runs the test suite on relatively powerful
x86 PCs, so it's probably making timing assumptions that don't hold on
slower CPUs.

On one hand, yes, of course we want tests that reliably pass. On the
other hand, Debian's self-imposed requirements say that every package
must work on every architecture where it's successfully built, and for
the less-widely-used architectures (particularly armhf) the build-time
tests are the only evidence we have that a package can work (nobody is
routinely testing the full GUI on 32-bit ARM). Realistically our choices
are tests that aren't fully reliable, or no tests at all; neither of
these is a desirable situation to be in, so it's a choice between two
bad options.

I've queued a commit for the next upload to disable the
wayland-subsurface test, which seems to be particularly bad on armhf for
whatever reason.

     smcv

The option that might require give-backs for a DSA is worse, and armhf
won't be the first release architecture where mutter build-time tests
are run with failures ignored.

wayland-keyboard failed in 50.2-1, and also failed on arm64 in 50.1-1.

wayland-stable-rounding failed in 50.1-1.

cu
Adrian

All arm buildds are shared between arm64 and armhf, which does not make
CPU speed a prime suspect for why armhf is more flaky than arm64.

cu
Adrian

Hello,

Bug #1138999 in mutter reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/mutter/-/commit/611319eb00b83dbbe8fca3acfa5c405b3c6f302f
------------------------------------------------------------------------
d/rules: Ignore build-time test results on armhf

This test suite has never been completely stable, particularly on armhf
for whatever reason. The full GNOME UI is not necessarily practically
useful on 32-bit systems, but dropping architectures here requires a
coordinated transition among several packages, so let's not try to do
that at the same time as an ongoing transition.

Closes: #1138999
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1138999

Hello,

Bug #1138999 in mutter reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/mutter/-/commit/ce66bd0c623f6e9ee5f4b1040f241ac9aa435025
------------------------------------------------------------------------
d/rules, d/tests: Give up on using the upstream test suite as a QA gate

In the past we've tried to curate the tests and separate them into
reliable and flaky, but some of the parts that are unreliable seem to be
in common code like setup/teardown.

Run the tests anyway, even if their result can't be an automated QA gate:
that will hopefully let us distinguish between architectures that mostly
work, and architectures (if any) that don't work at all.

Closes: #1121518, #1138999
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1138999

We believe that the bug you reported is fixed in the latest version of
mutter, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1138999@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie <smcv@debian.org> (supplier of updated mutter package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 08 Jun 2026 15:10:29 +0100
Source: mutter
Architecture: source
Version: 50.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Simon McVittie <smcv@debian.org>
Closes: 1121518 1138999 1139266
Changes:
 mutter (50.2-3) unstable; urgency=medium
 .
   * Team upload
   * d/p/wayland-Only-schedule-a-single-cursor-location-update.patch
     d/p/wayland-Drop-semi-temporary-variable.patch:
     Add patches proposed upstream to avoid (harmless) log spam in some
     situations (Closes: #1139266)
   * d/rules, d/tests: Give up on using the upstream test suite as a QA gate.
     In the past we've tried to curate the tests and separate them into
     reliable and flaky, but some of the parts that are unreliable seem
     to be in common code like setup/teardown.
     Run the tests anyway, even if their result can't be an automated QA
     gate: that will hopefully let us distinguish between architectures
     that mostly work, and architectures (if any) that don't work at all.
     (Closes: #1121518, #1138999)
   * d/tests/libmutter-18-dev:
     Reinstate a superficial autopkgtest for the -dev package.
     This checks that dependencies are met and pkgconf succeeds. Before
     GNOME 50, the equivalent test used meta_is_wayland_compositor(), but
     that no longer exists, so call a different harmless function instead.
Checksums-Sha1:
 8a590936c7693f987a86246d1b41393dc63c7376 4949 mutter_50.2-3.dsc
 50e589bfd9855efdaa96ed0d28e8ac3297d5ddc4 85828 mutter_50.2-3.debian.tar.xz
 7d2a53c1fa1844093ad18ce81267e980dc7d85c8 15696868 mutter_50.2-3.git.tar.xz
 74671d3ed0f73887ffb2e4c98068f11e691931cd 17480 mutter_50.2-3_source.buildinfo
Checksums-Sha256:
 03e0eddcd7fa6a7112d55cf111503d74f4b5fccdacffe028efb881cd280550f1 4949 mutter_50.2-3.dsc
 8fd27b8030cb9b20cd98dd2f91690f5ba6f4378f1ac283fc579e77a96a510c77 85828 mutter_50.2-3.debian.tar.xz
 3df9b8830b00fcc4c2217895e45423389e8a88642974b5e6ed1ade2556b9af91 15696868 mutter_50.2-3.git.tar.xz
 7181a7fbc55ac7a9a78b34ce21464fd84f8a66ad627ea3b285e751b5afcf2103 17480 mutter_50.2-3_source.buildinfo
Files:
 6e213a4d16374ce24a9ba821082b697c 4949 x11 optional mutter_50.2-3.dsc
 f757dcd75231d2786858e6ff90ec6f2a 85828 x11 optional mutter_50.2-3.debian.tar.xz
 1f915cfe8cd2afa8d6e788718f145380 15696868 x11 None mutter_50.2-3.git.tar.xz
 c26675409b2ba31db1dc6690672175df 17480 x11 optional mutter_50.2-3_source.buildinfo
Git-Tag-Info: tag=af86e4ce1e6c90dd9a8c0662790cd15601159f9d fp=7a073ad1ae694fa25bff62e5235c099d3eb33076
Git-Tag-Tagger: Simon McVittie <smcv@debian.org>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmomzfcACgkQYG0ITkaD
wHmaCRAAyMJDT71+9xwQT3DQ0PGMfV9wq+46XKIB+fRiO+uFGkuOGtniBTqwteCS
n/yFH/wrMRN2Fu8GIBgtn7XueB7J17iPmU+bYaEQE3qMd1S8wwDFlMbsI74NbcCu
ax0h2sYtuuQl7A/kraK5gg9UiR8bsOnw03cP5yK3ZAyawl3TX34f3pMAaek5s/wA
TWRVPGtQJRofKoK7SbVXHmwgzDsNtk8QaedVMo6VubxxZGEYpL77fXkxSNQujsIO
lc47MgGazx6BUnwnUupnr0p3n/Ks4eGuAImz8ykmIu3hfBZT1Bz37vyY+hVrUcZU
85Uy89KXEwWb4Kpm5skWkk27yiEpaN2b7rdRIuJU4EQAtn/ZfqTo+SvUgr7TugzD
AaTYcxyLbWqtqMMSDW/92fjGbkgVCS3IWfqtf5cJ8XhLuHckmrQqPDcn1xdDX045
nWABVnihIZGc08+dMMYslv1JcM1QJemTy69xvQWqqwXPfcyptSgM+FB+72f8M2k5
Xd/IElCJsaD7msjq8Rd/mjNiquZRprGeNudvUiJRxipaTmfLoJOe22Wj0/iybrZn
rc27VghZMemvm5LnMKLpXNX9otO4J6xrDTPErhyRhACvzjjf42qunJ0qWNZ9U9sI
0/6gM/ZbvIjLFBXD5hw0bNqmc9ULwWHDMdJI1Q31m1dLQ4ZQlTQ=
=/GDy
-----END PGP SIGNATURE-----