unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37553-done@debbugs.gnu.org
Subject: [bug#37553] [PATCH] inferior: Change to use the (guix repl) module.
Date: Sun, 06 Oct 2019 09:46:27 +0100	[thread overview]
Message-ID: <874l0mp8gs.fsf@cbaines.net> (raw)
In-Reply-To: <87imp7jy01.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]


Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> Christopher Baines <mail@cbaines.net> skribis:
>
>> Yep, I've been experimenting with loading older revisions in to the Guix
>> Data Service, and this is one of the issues I came across.
>
> Nice!  I’ve been thinking we should have time-traveling continuous
> integration.  Like checking that we can build some Guix revision of the
> past in between two ‘core-updates’ merges.
>
> It would also be useful to flag known-bad revisions, but in a way the
> Data Service is already doing that for recent revisions.

So I've been looking at retrying failed jobs in the Guix Data Service,
there are a few where it's just networking issues talking to Savannah.

I guess it could be useful to have a list of revisions which can't be
used through guix pull or a channel, and that information could also be
used in the Guix Data Service.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  reply	other threads:[~2019-10-06  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-29 13:01 [bug#37553] [PATCH] inferior: Change to using guix-repl Christopher Baines
2019-09-29 15:20 ` [bug#37553] [PATCH] inferior: Change to use the (guix repl) module Christopher Baines
2019-09-29 15:57 ` Christopher Baines
2019-10-01  8:56   ` Ludovic Courtès
2019-10-01 19:26     ` bug#37553: " Christopher Baines
2019-10-02  9:30       ` [bug#37553] " Ludovic Courtès
2019-10-06  8:46         ` Christopher Baines [this message]
2019-10-06  8:58           ` 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=874l0mp8gs.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=37553-done@debbugs.gnu.org \
    --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).