From: ng0 <ng0@infotropique.org>
To: 28231@debbugs.gnu.org
Subject: bug#28231: log-file: echo name at the end of builds
Date: Fri, 25 Aug 2017 14:55:24 +0000 [thread overview]
Message-ID: <20170825145524.wt5iqxvzvgpwnsj2@abyayala> (raw)
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
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.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-08-25 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 14:55 ng0 [this message]
2017-08-25 15:04 ` bug#28231: log-file: echo name at the end of builds ng0
2018-02-05 11:20 ` Ludovic Courtès
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=20170825145524.wt5iqxvzvgpwnsj2@abyayala \
--to=ng0@infotropique.org \
--cc=28231@debbugs.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).