From: Ricardo Wurmus <rekado@elephly.net>
To: Brenton Horne <brentonhorne77@gmail.com>
Cc: 27067@debbugs.gnu.org
Subject: bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged
Date: Thu, 25 May 2017 23:30:19 +0200 [thread overview]
Message-ID: <87fufsvd3o.fsf@elephly.net> (raw)
In-Reply-To: <CANb+58JqyVBOB0U=1cBcXUm=Y6F+xHh0Yu_iDcbLzk0xpWhN7A@mail.gmail.com>
Brenton Horne <brentonhorne77@gmail.com> writes:
> For example,
> `guix pull && guix package -u` has taken up to 12 hours to run for me
> before, so if it fails and doesn't log it can be quite an irritating waste
> of time and deter people from filing invaluable bug reports about issues
> they've experienced with guix.
“guix package” really does the same as “guix build” and if it fails the
failure will be recorded in the log that belongs to the derivation that
failed.
Not sure about “guix pull”, though.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-05-25 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 7:54 bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged Brenton Horne
2017-05-25 16:41 ` Arun Isaac
2017-05-25 17:05 ` bug#27067: Reply to Arun Isaac's reply Brenton Horne
[not found] ` <a7836b86.AEAAKjHnUF4AAAAAAAAAAAPE-g8AAAACwQwAAAAAAAW9WABZJwlc@mailjet.com>
[not found] ` <CANb+58K6AENjXCrPF=gE=ou+AKE=G+R9+qscPjj3vQjSE-eijQ@mail.gmail.com>
[not found] ` <3b96388e.AEAAKj4NjDIAAAAAAAAAAAPE-g8AAAACwQwAAAAAAAW9WABZJx4e@mailjet.com>
2017-05-25 18:25 ` bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged Brenton Horne
2017-05-25 20:10 ` Ricardo Wurmus
2017-05-25 20:33 ` Brenton Horne
2017-05-25 21:30 ` Ricardo Wurmus [this message]
2017-05-30 20:14 ` Ludovic Courtès
2018-12-17 9:30 ` swedebugia
2018-12-18 11:21 ` 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=87fufsvd3o.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=27067@debbugs.gnu.org \
--cc=brentonhorne77@gmail.com \
/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).