From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#31974: If a phase returns #f, a warning is issued, but the build continues Date: Sun, 19 Aug 2018 15:53:03 +0200 Message-ID: <876006ihts.fsf@gnu.org> References: <87efgu8clc.fsf@netris.org> <87600qstkn.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40737) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1frO9b-0003C4-AQ for bug-guix@gnu.org; Sun, 19 Aug 2018 09:54:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1frO9a-0005ew-LH for bug-guix@gnu.org; Sun, 19 Aug 2018 09:54:03 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:49466) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1frO9a-0005er-I9 for bug-guix@gnu.org; Sun, 19 Aug 2018 09:54:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1frO9a-0007nR-Fu for bug-guix@gnu.org; Sun, 19 Aug 2018 09:54:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87600qstkn.fsf@netris.org> (Mark H. Weaver's message of "Fri, 03 Aug 2018 23:23:52 -0400") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 31974@debbugs.gnu.org Mark H Weaver skribis: > Mark H Weaver writes: > >> I just noticed that I made a mistake in commit >> d8a3b1b9e847d4a44d2695f95af77170d4d2788f, which changed 'gnu-build' in >> (guix build gnu-build-system) to issue a warning if a phase returns a >> value other than #t. >> >> The result is that if a phase returns a value other than #t, a warning >> is issued, but the build nonetheless continues to the next phase, and >> the build could ultimately "succeed" even some phases returned #f. >> >> In other words, the return values of phases are effectively ignored, >> except for the warning, so the only way to cause a build with phases to >> fail is to raise an exception. > > This should be fixed by commit 82230603ce06de7aa3e4aef2fa093a6dbf0ef8df > in core-updates. Cool, thanks for not forgetting! :-) Ludo=E2=80=99.