From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brenton Horne 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: Fri, 26 May 2017 06:33:32 +1000 Message-ID: References: <87inkovgt7.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c05430e70241305505f2280" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48398) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDzSQ-0008AD-3T for bug-guix@gnu.org; Thu, 25 May 2017 16:34:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dDzSM-0005xE-1R for bug-guix@gnu.org; Thu, 25 May 2017 16:34:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:35504) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dDzSL-0005xA-TR for bug-guix@gnu.org; Thu, 25 May 2017 16:34:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dDzSL-000349-Ns for bug-guix@gnu.org; Thu, 25 May 2017 16:34:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87inkovgt7.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 27067@debbugs.gnu.org --94eb2c05430e70241305505f2280 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable This feature request isn't specific to guix build (it was low priority to me as I knew it at least had the ability to log, thanks for telling me it automatically does but it doesn't really change this feature request), it's asking for all guix commands with substantial output to automatically log. I have never run guix build, but I know that some guix commands run for a very long time and if they fail and do not log it, it can be quite irritating to have to re-run it and use tee to log its output. 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. On 26 May 2017 at 06:10, Ricardo Wurmus wrote: > > Brenton Horne writes: > > > As I understand it only the guix build command has an option to log > output > > to a file. > > Actually, the output of =E2=80=9Cguix build=E2=80=9D is indeed stored by = default. > You can get it by asking for the logs for a given derivation. > > For example: > > # build something, please > guix build --no-substitutes samtools > =E2=80=A6 > # show me the derivation > guix build -d samtools > # show me the location of the matching log > guix build --log-file $(guix build -d samtools) > > Does this solve the feature request? > > -- > Ricardo > > GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC > https://elephly.net > > --=20 Thanks for your time, Brenton --94eb2c05430e70241305505f2280 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This feature request isn't specific to guix build (it = was low priority to me as I knew it at least had the ability to log, thanks= for telling me it automatically does but it doesn't really change this= feature request), it's asking for all guix commands with substantial o= utput to automatically log. I have never run guix build, but I know that so= me guix commands run for a very long time and if they fail and do not log i= t, it can be quite irritating to have to re-run it and use tee to log its o= utput. 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.=C2=A0

On 26 May 2017 at 06:10, Ri= cardo Wurmus <rekado@elephly.net> wrote:

Brenton Horne <brentonhorne7= 7@gmail.com> writes:

> As I understand it only the guix build command has an option to log ou= tput
> to a file.

Actually, the output of =E2=80=9Cguix build=E2=80=9D is indeed stored by de= fault.
You can get it by asking for the logs for a given derivation.

For example:

=C2=A0 =C2=A0 # build something, please
=C2=A0 =C2=A0 guix build --no-substitutes samtools
=C2=A0 =C2=A0 =E2=80=A6
=C2=A0 =C2=A0 # show me the derivation
=C2=A0 =C2=A0 guix build -d samtools
=C2=A0 =C2=A0 # show me the location of the matching log
=C2=A0 =C2=A0 guix build --log-file $(guix build -d samtools)

Does this solve the feature request?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6=C2=A0 2150 197A 5888 235F ACAC
https:= //elephly.net




--
Thanks for your time,
Brenton
--94eb2c05430e70241305505f2280--