From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 54786@debbugs.gnu.org
Subject: bug#54786: Installation tests are failing
Date: Sun, 01 May 2022 15:26:20 +0200 [thread overview]
Message-ID: <875ymp4c5f.fsf@gnu.org> (raw)
In-Reply-To: <875ymqwwq8.fsf@gnu.org> (Mathieu Othacehe's message of "Sat, 30 Apr 2022 15:02:07 +0200")
Hi,
Mathieu Othacehe <othacehe@gnu.org> skribis:
> Thanks for the fix! The jami and jami-provisioning tests are also broken
> because of what looks like to be the same issue:
>
> One does not simply initialize the client: Another daemon is detected
> /gnu/store/01phrvxnxrg1q0gxa35g7f77q06crf6v-shepherd-marionette.scm:1:1718: ERROR:
> 1. &action-exception-error:
> service: jami
> action: start
> key: match-error
> args: ("match" "no matching pattern" #f)
> Jami Daemon 11.0.0, by Savoir-faire Linux 2004-2019
> https://jami.net/
> [Video support enabled]
> [Plugins support enabled]
Yes, I noticed that, but I’m not sure how to apply a similar workaround.
> I think we don't have the right approach here: we should check that the
> system tests are passing before pushing series and not adapt the tests
> afterwards.
Yes, apologies for that.
> Historically this was difficult because the system tests were often in a
> semi-broken state. Before the Shepherd update the tests were however all
> passing (modulo rare intermittent failures).
>
> As it's not always obvious what's going to break the system tests and
> what's not (simple package update can easily break them), it would be
> really nice to have mandatory commit verification.
>
> The mumi/cuirass gateway that has already been discussed could really
> help us here. If some people are motivated, we could split the work and
> introduce such a mechanism.
Yes, I agree; an “always green” ‘master’ branch would be great.
Do you have milestones in mind for “commit verification”?
As I see it, the difficulty is that we’ve been looking at a horizon of
features à la GitLab-CI without being quite sure how to get there (apart
from deploying GitLab or a similar tool, that is).
A first step that comes to mind would be an easier way to set up
transient jobsets for a branch (or, ideally, for an issue: the thing
would apply patches and create the branch).
Thoughts?
(Maybe worth moving to guix-devel.)
Ludo’.
next prev parent reply other threads:[~2022-05-01 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 9:51 bug#54786: Installation tests are failing Mathieu Othacehe
2022-04-08 15:10 ` Mathieu Othacehe
2022-04-28 7:22 ` Mathieu Othacehe
2022-04-28 19:19 ` Ludovic Courtès
2022-04-29 19:50 ` Ludovic Courtès
2022-04-30 13:02 ` Mathieu Othacehe
2022-05-01 13:26 ` Ludovic Courtès [this message]
2022-05-25 3:43 ` Maxim Cournoyer
2022-05-28 21:29 ` Ludovic Courtès
2022-05-31 16:44 ` bug#54786: [PATCH] services: jami: Modernize to adjust to Shepherd 0.9+ changes Maxim Cournoyer
2022-06-01 9:54 ` bug#54786: Installation tests are failing Ludovic Courtès
2022-06-01 13:10 ` Maxim Cournoyer
2022-06-02 13:13 ` Ludovic Courtès
2022-06-02 17:24 ` Maxim Cournoyer
2022-06-02 20:43 ` Ludovic Courtès
2022-06-04 4:37 ` Maxim Cournoyer
2022-06-07 14:00 ` Ludovic Courtès
2022-06-08 0:58 ` bokr
2022-06-11 4:18 ` Maxim Cournoyer
2022-08-09 14:20 ` Mathieu Othacehe
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=875ymp4c5f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54786@debbugs.gnu.org \
--cc=othacehe@gnu.org \
/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).