From: Ricardo Wurmus <rekado@elephly.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 33737@debbugs.gnu.org
Subject: bug#33737: do not attempt to build a package known to be broken
Date: Sun, 16 Dec 2018 22:55:30 +0100 [thread overview]
Message-ID: <87imztw2zx.fsf@elephly.net> (raw)
In-Reply-To: <20181216211451.7e15fdc7@scratchpost.org>
Danny Milosavljevic <dannym@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
next prev parent reply other threads:[~2018-12-17 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 4:41 bug#33737: do not attempt to build a package known to be broken Ricardo Wurmus
2018-12-15 18:54 ` Björn Höfling
2018-12-15 19:39 ` znavko
2018-12-16 20:14 ` Danny Milosavljevic
2018-12-16 21:55 ` Ricardo Wurmus [this message]
2018-12-18 10:50 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imztw2zx.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=33737@debbugs.gnu.org \
--cc=dannym@scratchpost.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.