From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: bug#33737: do not attempt to build a package known to be broken
Date: Sun, 16 Dec 2018 22:55:30 +0100
Message-ID: <87imztw2zx.fsf@elephly.net>
References: <87efakyb26.fsf@elephly.net>
	<20181216211451.7e15fdc7@scratchpost.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57906)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gYhv4-0004o4-Sf
	for bug-guix@gnu.org; Sun, 16 Dec 2018 20:42:08 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gYhv0-0002mj-Pt
	for bug-guix@gnu.org; Sun, 16 Dec 2018 20:42:06 -0500
Received: from debbugs.gnu.org ([208.118.235.43]:46468)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gYhv0-0002mD-EH
	for bug-guix@gnu.org; Sun, 16 Dec 2018 20:42:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gYhv0-0000Nk-BU
	for bug-guix@gnu.org; Sun, 16 Dec 2018 20:42:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.33737.B33737.15450109091448@debbugs.gnu.org>
In-reply-to: <20181216211451.7e15fdc7@scratchpost.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 33737@debbugs.gnu.org


Danny Milosavljevic <dannym@scratchpost.org> writes:

>> I propose that =E2=80=9Cguix publish=E2=80=9D should also convey informa=
tion 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 =E2=80=9C--fallback=E2=80=9D 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 a=
ctual
> 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=E2=80=99t know how we could distinguish different kinds of build fail=
ures
with the current daemon.

--
Ricardo