From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix build output insufficient
Date: Wed, 12 Sep 2018 19:09:39 +0200 [thread overview]
Message-ID: <87sh2e7ics.fsf@gnu.org> (raw)
In-Reply-To: <875zzcl09b.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 11 Sep 2018 13:52:16 +0200")
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
Hello,
Ricardo Wurmus <rekado@elephly.net> skribis:
>> On latest
>>
>> ./pre-inst guix package -i something
>>
>> The new color scheme is nice for output. But I miss the old build
>> logs. How do I get them back?
>
> The build logs are stored by the daemon. You can get their location by
> doing
>
> guix build --log-file something
What about immediately giving the file name of the log, as with the
patch attached? Several people have already mentioned not knowing about
‘guix build --log-file’ so this would probably be helpful.
Thanks for bringing colors and minimalism to the tools’ output! :-)
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1170 bytes --]
diff --git a/guix/ui.scm b/guix/ui.scm
index 1bbd37c25..98425eaff 100644
--- a/guix/ui.scm
+++ b/guix/ui.scm
@@ -1708,12 +1708,15 @@ phase announcements and replaces any other output with a spinner."
(string-append
(proc "Building " 'BLUE 'BOLD)
(match:substring m 2) "\n")))
- ("^(@ build-failed) (.*) (.*)"
+ ("^(@ build-failed) ([[:graph:]]+*) (.*)"
#:transform
,(lambda (m)
- (string-append
- (proc "Build failed: " 'RED 'BOLD)
- (match:substring m 2) "\n")))
+ (let ((drv (match:substring m 2)))
+ (string-append
+ (proc "Build failed: " 'RED 'BOLD)
+ drv "\n")
+ (info (G_ "build log available at '~a'~%")
+ (log-file #f (pk 'drv drv)))))) ;XXX: 1st arg
("^(@ build-succeeded) (.*) (.*)"
#:transform
,(lambda (m)
next prev parent reply other threads:[~2018-09-12 17:09 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
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 [this message]
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=87sh2e7ics.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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).