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

Previous Next

Full log

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

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: Ricardo Wurmus <rekado <at> elephly.net>
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 21:14:51 +0100

[Message part 1 (text/plain, inline)]

On Fri, 14 Dec 2018 05:41:37 +0100
Ricardo Wurmus <rekado <at> elephly.net> wrote:

> The default use case is for users to have substitutes enabled and to
> fetch binaries from a build farm.  The build farm tries to build all
> packages, but not all builds succeed.  The daemon caches build failures.
> 
> This information, however, is not available for users.  The default
> behaviour of Guix is to attempt building the package locally.  This is
> fine for packages that the build farm hasn’t attempted yet, but it is a
> waste of time when the build has already been attempted without success.
> 
> 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.

[Message part 2 (application/pgp-signature, inline)]

Previous Next

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