unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41668@debbugs.gnu.org, Brice Waegeneire <brice@waegenei.re>
Subject: bug#41668: Failing test: gui-installed-desktop-os-encrypted
Date: Mon, 08 Jun 2020 10:47:42 +0200	[thread overview]
Message-ID: <87zh9eaqq9.fsf@gnu.org> (raw)
In-Reply-To: <87blluslc8.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 07 Jun 2020 21:54:31 +0200")


Hey Ludo,

> How did you do it in the example above?  Perhaps we can have a local
> hack specifically in the installer (otherwise we’d find ourselves
> duplicating syslog-related logic there.)

I used a custom re-implementation of "invoke/quiet" printing every line
on the syslog port. Maybe, we could enable such a mechanism only during
the tests.

> I don’t have good ideas for (1), although I think the speedups induced
> by the new image API might help.

Yes, that's for sure making the debug more comfortable!

> As for (2), I think it’s kind of a problem of CI in general, connected
> with the fact that we’re all somewhat busy building stuff rather than
> waiting for CI notifications to act on.  :-)
>
> That’s my impression, but I’d really like to hear from people with
> experience in CI and/or the system tests.

Totally agree. When submitting patches to Linux for instance, the CI is
able to reply to the patch mail, and warn about any failures. An other
difference is that patches are often kept in the maintainer 'staging'
branches until the CI is over.

I don't know if Guix is a big enough project to appoint some maintainers
that would periodically merge their branches to 'master' or if it would
just be a huge burden. Something we need to discuss in the future maybe.

> Perfect, thanks!

Anyway, thanks for your fast review :)

Mathieu




  reply	other threads:[~2020-06-08  8:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 18:52 bug#41668: Failing test: gui-installed-desktop-os-encrypted Brice Waegeneire
2020-06-06 10:16 ` Mathieu Othacehe
2020-06-07 15:28   ` Mathieu Othacehe
2020-06-07 19:54     ` Ludovic Courtès
2020-06-08  8:47       ` Mathieu Othacehe [this message]
2020-06-08 13:24         ` Mathieu Othacehe
2020-06-09 11:18           ` Mathieu Othacehe
2020-06-09 14:22             ` Ludovic Courtès
2020-06-09 16:01               ` Mathieu Othacehe
2020-06-08 14:26       ` Danny Milosavljevic
2020-06-09 14:24         ` Ludovic Courtès
2020-06-14 16:16   ` Mathieu Othacehe
2020-06-14 20:28     ` Ludovic Courtès
2020-06-16 15:40       ` Mathieu Othacehe
2020-06-17 12:33         ` Ludovic Courtès
2020-09-11  7:32           ` Mathieu Othacehe
2020-09-11 14:42             ` Ludovic Courtès

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=87zh9eaqq9.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=41668@debbugs.gnu.org \
    --cc=brice@waegenei.re \
    --cc=ludo@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).