From: Ricardo Wurmus <rekado@elephly.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix build output insufficient
Date: Wed, 12 Sep 2018 08:52:36 +0200 [thread overview]
Message-ID: <87r2hzjjgr.fsf@elephly.net> (raw)
In-Reply-To: <20180911162321.077cfefb@scratchpost.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
>>
>> 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 “diamond” package and ran
guix package -i diamond
This ends with
Build failed: /gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.drv
guix package: error: build failed: build of `/gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.drv' failed
So I ran
guix build --log-file /gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-diamond-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’s nothing that the build-output-port should try to do on its own,
in my opinion, because it really just transforms output lines.)
--
Ricardo
next prev parent reply other threads:[~2018-09-12 6:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 8:26 Guix build output insufficient Pjotr Prins
2018-09-11 9:04 ` Pjotr Prins
2018-09-11 9:55 ` Danny Milosavljevic
2018-09-11 10:41 ` Pierre Neidhardt
2018-09-11 11:59 ` Devan Carpenter
2018-09-11 11:52 ` Ricardo Wurmus
2018-09-11 14:23 ` Danny Milosavljevic
2018-09-12 6:52 ` Ricardo Wurmus [this message]
2018-09-12 15:25 ` Pjotr Prins
2018-09-13 6:45 ` Pjotr Prins
2018-09-13 7:23 ` Ricardo Wurmus
2018-09-12 17:09 ` Ludovic Courtès
2018-09-12 17:25 ` Ricardo Wurmus
2018-09-12 17:34 ` Tobias Geerinckx-Rice
2018-09-12 17:42 ` Tobias Geerinckx-Rice
2018-09-12 17:52 ` Ricardo Wurmus
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=87r2hzjjgr.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.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 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).