GNU bug report logs - #33737
do not attempt to build a package known to be broken

Previous Next

Full log

Message #17 received at 33737 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 33737 <at> debbugs.gnu.org
Subject: Re: bug#33737: do not attempt to build a package known to be broken
Date: Sun, 16 Dec 2018 22:55:30 +0100

Danny Milosavljevic <dannym <at> scratchpost.org> writes:

>> I propose that “guix publish” should also convey information about
>> failed builds.  The Guix client can then abort right away without
>> wasting time and power to attempt a doomed build.  Users may override
>> this with “--fallback” or a new option.
>
> As long as we distinguish transient build machine errors (disk full, can't
> resolve hostname, too many names in directory, no inodes left etc) from actual
> errors in the source code, +1.

I was thinking of something very simple.  The daemon is already capable
of caching build failures; I think it may be good to simply pass that
information on to clients.

I don’t know how we could distinguish different kinds of build failures
with the current daemon.

--
Ricardo

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.