unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@infotropique.org>
Cc: 28231-done@debbugs.gnu.org
Subject: bug#28231: log-file: echo name at the end of builds
Date: Mon, 05 Feb 2018 12:20:38 +0100	[thread overview]
Message-ID: <877errfzsp.fsf@gnu.org> (raw)
In-Reply-To: <20170825145524.wt5iqxvzvgpwnsj2@abyayala> (ng0@infotropique.org's message of "Fri, 25 Aug 2017 14:55:24 +0000")

Hello,

ng0 <ng0@infotropique.org> skribis:

> When a build invoked with --no-build-hook -K --log-file fails, this is the
> last output you'll see:
>
> 14:01.58 565 compiler warnings present.
> mach configuremachphase `configure' failed after 869.5 seconds
> note: keeping build directory `/tmp/guix-build-thunderbird-52.2.1.drv-0'
> builder for `/gnu/store/n7qma1ypp2px1shd88r736ykjg5dngll-thunderbird-52.2.1.drv' failed with exit code 1
> @ build-failed /gnu/store/n7qma1ypp2px1shd88r736ykjg5dngll-thunderbird-52.2.1.drv - 1 builder for `/gnu/store/n7qma1ypp2px1shd88r736ykjg5dngll-thunderbird-52.2.1.drv' failed with exit code 1
> guix build: error: build failed: build of `/gnu/store/n7qma1ypp2px1shd88r736ykjg5dngll-thunderbird-52.2.1.drv' failed
>
> As far as I remember from builds I have aborted at the beginning, the
> logfile name is displayed when the build process beginns.
>
> In my opinion we should also display them at the end builds (however they end).
> If we don't record logs of failed builds, we should start doing that.

I don’t think it’s necessary, we can always get the file name with “guix
build --log-file”, can’t we?

Ludo’.

      parent reply	other threads:[~2018-02-05 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 14:55 bug#28231: log-file: echo name at the end of builds ng0
2017-08-25 15:04 ` ng0
2018-02-05 11:20 ` Ludovic Courtès [this message]

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=877errfzsp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=28231-done@debbugs.gnu.org \
    --cc=ng0@infotropique.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).