GNU bug report logs - #76976
Mutter build failure

Previous Next

To reply to this bug, email your comments to 76976 AT debbugs.gnu.org.
There is no need to reopen the bug first.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: bug-guix <at> gnu.org
Cc: vivien <at> planete-kraus.eu, Liliana Marie Prikler <liliana.prikler <at> gmail.com>,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Subject: Mutter build failure
Date: Wed, 12 Mar 2025 12:43:22 +0100

Hello,

when trying to upgrade my system, I see the following build failure:

...
Summary of Failures:

135/191 mutter:core+mutter/backends/native / native-unit                                               FAIL            0.33s   killed by signal 6 SIGABRT

Ok:                 185
Expected Fail:      5
Fail:               1
Unexpected Pass:    0
Skipped:            0
Timeout:            0
...
guix build: Fehler: build of `/gnu/store/fx8ya4jhrdjw3a1bm5g3fjx301rzmxkn-mutter-46.8.drv' failed

If guix tried to build it locally, that is because it is not available
on the bordeaux build farm.

I do not even use Gnome, just gdm as a login manager for an XFCE
environment, and not being able to upgrade is quite serious.
My previous, working system comes from commit
3d34fde47f9039fcecbb338e45782722f10e5e36 .
So supposedly this comes from the recent gnome-team merge.

Andreas

Message #8 received at 76976 <at> debbugs.gnu.org (full text, mbox):

From: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
To: Andreas Enge <andreas <at> enge.fr>, 76976 <at> debbugs.gnu.org
Cc: vivien <at> planete-kraus.eu, Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Subject: Re: Mutter build failure
Date: Wed, 12 Mar 2025 21:03:21 +0100

Am Mittwoch, dem 12.03.2025 um 12:43 +0100 schrieb Andreas Enge:
> Hello,
> 
> when trying to upgrade my system, I see the following build failure:
> 
> ...
> Summary of Failures:
> 
> 135/191 mutter:core+mutter/backends/native / native-
> unit                                               FAIL           
> 0.33s   killed by signal 6 SIGABRT
> 
> Ok:                 185
>  * Expected Fail:      5
> Fail:               1
> Unexpected Pass:    0
> Skipped:            0
> Timeout:            0
> ...
> guix build: Fehler: build of
> `/gnu/store/fx8ya4jhrdjw3a1bm5g3fjx301rzmxkn-mutter-46.8.drv' failed
> 
> If guix tried to build it locally, that is because it is not
> available on the bordeaux build farm.
> 
> I do not even use Gnome, just gdm as a login manager for an XFCE
> environment, and not being able to upgrade is quite serious.
> My previous, working system comes from commit
> 3d34fde47f9039fcecbb338e45782722f10e5e36 .
> So supposedly this comes from the recent gnome-team merge.
Yeah, this appears to be a flaky test. FWIW, a test by the same name is
already disabled for gnome-shell, so we should probably disable it.

Cheers

Message #11 received at 76976 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: vivien <at> planete-kraus.eu, 76976 <at> debbugs.gnu.org,
 Liliana Marie Prikler <liliana.prikler <at> gmail.com>
Subject: Re: Mutter build failure
Date: Thu, 13 Mar 2025 10:43:25 +0900

Hi,

Andreas Enge <andreas <at> enge.fr> writes:

> Hello,
>
> when trying to upgrade my system, I see the following build failure:
>
> ...
> Summary of Failures:
>
> 135/191 mutter:core+mutter/backends/native / native-unit FAIL 0.33s
> killed by signal 6 SIGABRT
>
> Ok:                 185
> Expected Fail:      5
> Fail:               1
> Unexpected Pass:    0
> Skipped:            0
> Timeout:            0
> ...
> guix build: Fehler: build of `/gnu/store/fx8ya4jhrdjw3a1bm5g3fjx301rzmxkn-mutter-46.8.drv' failed
>
> If guix tried to build it locally, that is because it is not available
> on the bordeaux build farm.
>
> I do not even use Gnome, just gdm as a login manager for an XFCE
> environment, and not being able to upgrade is quite serious.
> My previous, working system comes from commit
> 3d34fde47f9039fcecbb338e45782722f10e5e36 .
> So supposedly this comes from the recent gnome-team merge.

CI has a substitute for it; don't you use substitutes from Berlin as
well as Bordeaux? (that is the default).

W.r.t. the problem at hand, I've just rebuilt Mutter 5 times on my
machine (and had done so at least 10s of times as part of the gnome
updates to squash out test failures) without this test failing, so I
assume its timing sensitive.

Are you able to reproduce at will?  Could you please share the detailed
output of the error; you've posted only the summary of the test suite.

-- 
Thanks,
Maxim

Message #14 received at 76976 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: vivien <at> planete-kraus.eu, 76976 <at> debbugs.gnu.org,
 Liliana Marie Prikler <liliana.prikler <at> gmail.com>
Subject: Re: Mutter build failure
Date: Thu, 13 Mar 2025 11:46:30 +0100

Hello,

Am Thu, Mar 13, 2025 at 10:43:25AM +0900 schrieb Maxim Cournoyer:
> CI has a substitute for it; don't you use substitutes from Berlin as
> well as Bordeaux? (that is the default).

no, since I am offloading to a machine that is also part of the bordeaux
build farm, I have to avoid mixing the substitutes.

> Are you able to reproduce at will?  Could you please share the detailed
> output of the error; you've posted only the summary of the test suite.

It seems to happen systematically on two laptops on which I have tried.
The error message of the failing test is below.

Andreas


116/191 mutter:clutter+clutter/conform / gesture                                                       RUNNING       
>>> G_TEST_BUILDDIR=/tmp/guix-build-mutter-46.8.drv-0/build/src/tests/clutter/conform MALLOC_PERTURB_=106 LD_LIBRARY_PATH=/tmp/guix-build-mutter-46.8.drv-0/build/mtk/mtk:/tmp/guix-build-mutter-46.8.drv-0/build/cogl/cogl:/tmp/guix-build-mutter-46.8.drv-0/build/clutter/clutter:/tmp/guix-build-mutter-46.8.drv-0/build/cogl/cogl-pango:/tmp/guix-build-mutter-46.8.drv-0/build/src/tests:/tmp/guix-build-mutter-46.8.drv-0/build/src CLUTTER_ENABLE_DIAGNOSTIC=0 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 G_ENABLE_DIAGNOSTIC=0 G_TEST_SRCDIR=/tmp/guix-build-mutter-46.8.drv-0/mutter-46.8/src/tests/clutter/conform MESON_TEST_ITERATION=1 GSETTINGS_SCHEMA_DIR=/tmp/guix-build-mutter-46.8.drv-0/build/data MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 /tmp/guix-build-mutter-46.8.drv-0/build/src/tests/clutter/conform/gesture
――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
TAP version 14
# random seed: R02S3eb5f2f8c70caad43f58ce32b269a180
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory (GMemorySettingsBackend) for ‘gsettings-backend’
# libmutter-MESSAGE: Running Mutter Test (using mutter 46.8) as a Wayland display server
# GLib-GIO-DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
# libmutter-MESSAGE: Created surfaceless renderer without GPU
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
# libmutter-DEBUG: WL: loaded /gnu/store/6z3k3578w723ydpyqfprzprqy6jm60z9-egl-wayland-1.1.17/lib/libnvidia-egl-wayland.so.1:wl_eglstream_controller.
# libmutter-MESSAGE: Using Wayland display name 'mutter-test-display'
Window manager warning: Failed to set environment variable WAYLAND_DISPLAY for gnome-session: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist
# libmutter-MESSAGE: Added virtual monitor Meta-0
1..5
# Start of gesture tests
# libmutter-INFO: Acquired name org.gnome.Mutter.InputMapping
# libmutter-INFO: Acquired name org.gnome.Mutter.ServiceChannel
# GLib-GIO-DEBUG: GTask 0x237c940 (source object: 0x4ccda0, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
# GLib-GIO-DEBUG: GTask 0x237a800 (source object: 0x4ccda0, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
# GLib-GIO-DEBUG: GTask 0x2dae2b0 (source object: 0x4ccda0, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
# GLib-GIO-DEBUG: GTask 0x2db00d0 (source object: 0x4ccda0, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
ok 1 /gesture/disposed-while-active
# GLib-GIO-DEBUG: GTask 0x2dae2b0 (source object: 0x4ccda0, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
# GLib-GIO-DEBUG: GTask 0x3069ab0 (source object: 0x4ccda0, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
# GLib-GIO-DEBUG: GTask 0x3069ab0 (source object: 0x4ccda0, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
# GLib-GIO-DEBUG: GTask 0x3069ab0 (source object: 0x4ccda0, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
ok 2 /gesture/state-machine-move-to-waiting
# GLib-GIO-DEBUG: GTask 0x235cd20 (source object: 0x4ccda0, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
not ok /gesture/state-machine-move-to-cancelled-while-possible - Clutter-Conform:ERROR:../mutter-46.8/src/tests/clutter/conform/gesture.c:214:gesture_state_machine_move_to_cancelled_while_possible: 'clutter_gesture_get_state (gesture) == CLUTTER_GESTURE_STATE_POSSIBLE' should be TRUE
Bail out!
**
Clutter-Conform:ERROR:../mutter-46.8/src/tests/clutter/conform/gesture.c:214:gesture_state_machine_move_to_cancelled_while_possible: 'clutter_gesture_get_state (gesture) == CLUTTER_GESTURE_STATE_POSSIBLE' should be TRUE
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
116/191 mutter:clutter+clutter/conform / gesture                                                       FAIL            0.73s   killed by signal 6 SIGABRT

Message #19 received at 76976-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: vivien <at> planete-kraus.eu, 76976-done <at> debbugs.gnu.org,
 Liliana Marie Prikler <liliana.prikler <at> gmail.com>
Subject: Re: Mutter build failure
Date: Thu, 20 Mar 2025 23:22:17 +0900

Hi Andreas,

This should be fixed in commit 7a26e14ca2 ("gnu: mutter: Update to 46.9
and disable unreliable tests.").

If you still encounter problems, please open a new issue.

-- 
Thanks,
Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.