From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:41758) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iH2Nb-0006ZZ-H2 for guix-patches@gnu.org; Sun, 06 Oct 2019 04:59:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iH2Na-0000MC-JF for guix-patches@gnu.org; Sun, 06 Oct 2019 04:59:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:36727) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iH2Na-0000M7-GS for guix-patches@gnu.org; Sun, 06 Oct 2019 04:59:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iH2Na-0005ku-Cy for guix-patches@gnu.org; Sun, 06 Oct 2019 04:59:02 -0400 Subject: [bug#37553] [PATCH] inferior: Change to use the (guix repl) module. Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <20190929130128.18484-1-mail@cbaines.net> <20190929155728.27777-1-mail@cbaines.net> <87blv0sv2y.fsf@gnu.org> <87tv8sp8qn.fsf@cbaines.net> <87imp7jy01.fsf@gnu.org> <874l0mp8gs.fsf@cbaines.net> Date: Sun, 06 Oct 2019 10:58:15 +0200 In-Reply-To: <874l0mp8gs.fsf@cbaines.net> (Christopher Baines's message of "Sun, 06 Oct 2019 09:46:27 +0100") Message-ID: <87y2xygsig.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Christopher Baines Cc: 37553-done@debbugs.gnu.org Hi Chris, Christopher Baines skribis: > Ludovic Court=C3=A8s writes: > >> Hi, >> >> Christopher Baines 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=E2=80=99ve been thinking we should have time-traveling continuo= us >> integration. Like checking that we can build some Guix revision of the >> past in between two =E2=80=98core-updates=E2=80=99 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. Cool. > 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. Yes, thanks for looking into it! Ludo=E2=80=99.