unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 33737@debbugs.gnu.org
Subject: bug#33737: do not attempt to build a package known to be broken
Date: Sat, 15 Dec 2018 19:54:37 +0100	[thread overview]
Message-ID: <20181215195437.32313415@alma-ubu> (raw)
In-Reply-To: <87efakyb26.fsf@elephly.net>

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

On Fri, 14 Dec 2018 05:41:37 +0100
Ricardo Wurmus <rekado@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.

+1

Very good idea.

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-12-15 18:55 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 [this message]
2018-12-15 19:39   ` znavko
2018-12-16 20:14 ` Danny Milosavljevic
2018-12-16 21:55   ` Ricardo Wurmus
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

  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=20181215195437.32313415@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=33737@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).