From: Christopher Baines <mail@cbaines.net>
To: Christopher Baines <mail@cbaines.net>
Cc: rg@raghavgururajan.name, Vivien Kraus <vivien@planete-kraus.eu>,
liliana.prikler@gmail.com,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
69414@debbugs.gnu.org
Subject: [bug#69414] [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update
Date: Wed, 27 Mar 2024 12:23:29 +0000 [thread overview]
Message-ID: <87a5mjhncf.fsf@cbaines.net> (raw)
In-Reply-To: <877chvk35z.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi Christopher,
>>
>> Christopher Baines <mail@cbaines.net> writes:
>>
>>> Vivien Kraus <vivien@planete-kraus.eu> writes:
>>>
>>>> Hello,
>>>>
>>>> Le mercredi 20 mars 2024 à 10:42 +0000, Christopher Baines a écrit :
>>>>> Is there anything that needs to happen before gnome-team can be
>>>>> merged?
>>>>
>>>> There are concerning failures, such as lightdm, that must be
>>>> investigated. QA has also highlighted flaky tests in a bunch of
>>>> packages, and a time-bomb (kcalendarcore).
>>>
>>> I had a go to looking in to lightdm not building and it looks to maybe
>>> be dbus related, but I've got no idea really. Debian and nixpkgs don't
>>> even run the test suite as far as I can tell. I also tried the system
>>> test and that seems to pass. So maybe we raise the issue with upstream
>>> and disable the testsuite for now.
>>
>> I'd rather we spend a bit of time investigating the underlying failure
>> and engage with upstream if there's a need. Setting #:tests? #f is
>> easy, but it means the sometimes serious efforts that were needed to
>> enable the test suite go into bitrot, making it harder to re-enable at
>> a later time (thus unlikely).
>
> To elaborate on the point I'm trying to make, having spent a bit of time
> looking in to this specific issue, I don't think it's worth blocking the
> gnome-team merge over an issue with running the lightdm testsuite.
>
> Obviously if there's actually an issue with lightdm, then that's
> different. This is also somewhat personal since I've got almost no
> knowledge about lightdm or the dbus problems I suspect might be related.
Thanks to Vivian's patch (#69948) we're now building lightdm with an
older dbus.
I had a look for failures in QA and I didn't really see
anything. There's some issue with the tests for gtk on aarch64-linux,
not sure what's going on there, but I don't think that blocks merging.
Is there anything that needs to happen before gnome-team can be merged?
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2024-03-27 12:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 6:30 [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update Vivien Kraus via Guix-patches via
2024-03-18 19:26 ` [bug#69911] [PATCH gnome-team 1/6] gnu: folks: Update to 0.15.8 Vivien Kraus via Guix-patches via
2024-03-18 19:28 ` [bug#69911] [PATCH gnome-team 2/6] gnu: gnome-online-accounts: Update to 3.48.1 Vivien Kraus via Guix-patches via
2024-03-18 19:29 ` [bug#69911] [PATCH gnome-team 3/6] gnu: gnome-shell: Update to 44.10 Vivien Kraus via Guix-patches via
2024-03-18 19:30 ` [bug#69911] [PATCH gnome-team 4/6] gnu: gtkmm@3: Update to 3.24.9 Vivien Kraus via Guix-patches via
2024-03-18 19:34 ` [bug#69911] [PATCH gnome-team 5/6] gnu: template-glib: Update to 3.36.2 Vivien Kraus via Guix-patches via
2024-03-18 19:35 ` [bug#69911] [PATCH gnome-team 6/6] gnu: vala: Update to 0.56.16 Vivien Kraus via Guix-patches via
2024-03-20 10:42 ` [bug#69414] [bug#69911] [PATCH gnome-team 0/6] GNOME 44.10 update Christopher Baines
2024-03-20 12:25 ` Vivien Kraus via Guix-patches via
2024-03-20 13:58 ` [bug#69414] " Christopher Baines
2024-03-20 18:29 ` Maxim Cournoyer
2024-03-21 15:23 ` Christopher Baines
2024-03-27 12:23 ` Christopher Baines [this message]
2024-03-27 17:53 ` Liliana Marie Prikler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5mjhncf.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=69414@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).