From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: Guix build output insufficient
Date: Wed, 12 Sep 2018 08:52:36 +0200
Message-ID: <87r2hzjjgr.fsf@elephly.net>
References: <20180911082653.27gmposcatilbsuq@thebird.nl>
	<875zzcl09b.fsf@elephly.net>
	<20180911162321.077cfefb@scratchpost.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53832)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1fzz3m-0006B2-RZ
	for guix-devel@gnu.org; Wed, 12 Sep 2018 02:55:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1fzz1T-0005hX-Ci
	for guix-devel@gnu.org; Wed, 12 Sep 2018 02:53:14 -0400
Received: from sender-of-o51.zoho.com ([135.84.80.216]:21094)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <rekado@elephly.net>) id 1fzz1T-0005gD-0B
	for guix-devel@gnu.org; Wed, 12 Sep 2018 02:53:11 -0400
In-reply-to: <20180911162321.077cfefb@scratchpost.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>


Hi Danny,

> On Tue, 11 Sep 2018 13:52:16 +0200
> Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> The build logs are stored by the daemon.  You can get their location by
>> doing
>>=20
>>     guix build --log-file something
>
> Does this also work for failed builds - without rebuilding it again?

It does seem to work.  To test this I added (error "foo") to a build
phase in the =E2=80=9Cdiamond=E2=80=9D package and ran

   guix package -i diamond

This ends with

   Build failed:  /gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.2=
2.drv
   guix package: error: build failed: build of `/gnu/store/wk9qbhmdzs62mp40=
casrndcgm3p50m3b-diamond-0.9.22.drv' failed

So I ran

   guix build --log-file /gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-diamon=
d-0.9.22.drv

which gave me

   /var/log/guix/drvs/wk/9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.drv.=
bz2

which contains the build log for this failed build, including the "foo"
error message.

I would like this error log file location to be shown unprompted, but I
think we would need to change build.cc, so that BuildError prints it in
addition to the error message.

(That=E2=80=99s nothing that the build-output-port should try to do on its =
own,
in my opinion, because it really just transforms output lines.)

--=20
Ricardo