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

  • Done
  • quality assurance status badge
Details
5 participants
  • Arun Isaac
  • Brenton Horne
  • Ludovic Courtès
  • Ricardo Wurmus
  • swedebugia
Owner
unassigned
Submitted by
Brenton Horne
Severity
wishlist
B
B
Brenton Horne wrote on 25 May 2017 09:54
(address . bug-guix@gnu.org)
CANb+58KETz3PuoLKTozBaqPCLXbmHkgDCP4ERiAnQ9Evxe4fYQ@mail.gmail.com
Hi,

As I understand it only the guix build command has an option to log output
to a file. I would like to request that each guix command have the option
at least (if not automatic like it is for Gentoo's Portage package manager)
to log all output to a file. I believe this will help both users and
developers deal with bugs and alike in the package manager. I realize
people can already log all output using redirection like with:

COMMAND > output.log 2>&1


but with this method no output is shown at the command-line so users can't
track what guix is doing in real-time.

Thanks for your time,
Brenton
Attachment: file
A
A
Arun Isaac wrote on 25 May 2017 18:41
(name . Brenton Horne)(address . brentonhorne77@gmail.com)(address . 27067@debbugs.gnu.org)
50bb18f3.AEAAKjHnUF0AAAAAAAAAAAPE-hAAAAACwQwAAAAAAAW9WABZJwlc@mailjet.com
Toggle quote (8 lines)
> I realize people can already log all output using redirection like
> with:
>
> COMMAND > output.log 2>&1
>
> but with this method no output is shown at the command-line so users can't
> track what guix is doing in real-time.

Somebody else should comment on the feature request. But, for immediate
usage, to both log the output and see it in real-time, you could use
something like:

COMMAND | tee output.log
B
B
Brenton Horne wrote on 25 May 2017 19:05
Reply to Arun Isaac's reply
(address . 27067@debbugs.gnu.org)
CANb+58Ky8wBeB5D9YqBz4REvC+36tiWFwwsGOLtPR+7CrAqhGQ@mail.gmail.com
Hi,

Thanks. This feature would still be useful though, but your idea makes it
less urgent. Automatic logging still sounds like a good idea as the Guix
package manager is quite slow for some operations at the moment (not
criticising the developers of Guix, after all at this early stage of
development issues like this are to be expected), for me at least running
GuixSD in a QEMU VM with 8 GB RAM and 3 CPU cores (3.3 GHz i7 cores), so it
might save users interested in filing bug reports a lot of time (on
re-running the problem command with `| tee output.log` after it) if the
output was logged automatically. Saving users time will probably mean users
will be far more motivated and able to provide bug reports on issues they
experience, which is good for the entire Guix community as bugs would get
reported and resolved faster.

Thanks for your time,
Brenton
Attachment: file
B
B
Brenton Horne wrote on 25 May 2017 20:25
Re: 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
(address . 27067@debbugs.gnu.org)
CANb+58+xQZRQE1Sp1YFedj3awZNBHa=mnV5S=nscfGHrg-Ju+A@mail.gmail.com
I'm afraid I have no knowledge of Guile or Scheme. Looking at the Guile
manual seems to indicate to me it's a language quite unlike most languages
I've coded in. The only exception is that it does look a little like Emacs
Lisp.

On 26 May 2017 at 04:10, Arun Isaac <arunisaac@systemreboot.net> wrote:

Toggle quote (31 lines)
>
> Brenton Horne writes:
>
> > Thanks. I did ask in the #guix IRC channel first and no one provided this
> > solution (not using this as some criticism, I realize the IRC channel is
> > people volunteering their time to help others, just mentioning) and one
> > person agreed with my suggestion of reporting this as a feature request.
> > Still this feature would be useful, but your idea makes it less urgent.
> > Automatic logging still sounds like a good idea as Guix is quite slow for
> > some operations at the moment (not dissing the developers of Guix, after
> > all at this early stage of development issues like this are to be
> > expected), for me at least running GuixSD in a QEMU VM with 8 GB RAM and
> 3
> > CPU cores (3.3 GHz i7 cores), so it might save users interested in filing
> > bug reports a lot of time (on re-running the problem command with `| tee
> > output.log` after it) if the output was logged automatically. Saving
> users
> > time will probably mean users will be far more motivated and able to
> > provide bug reports on issues they experience, which is good for the
> entire
> > Guix community as bugs would get reported and resolved faster.
>
> You could work on this issue, and submit a patch. I'm sure that would be
> welcome.
>
> Regards,
> Arun Isaac.
>



--
Thanks for your time,
Brenton
Attachment: file
R
R
Ricardo Wurmus wrote on 25 May 2017 22:10
(name . Brenton Horne)(address . brentonhorne77@gmail.com)(address . 27067@debbugs.gnu.org)
87inkovgt7.fsf@elephly.net
Brenton Horne <brentonhorne77@gmail.com> writes:

Toggle quote (3 lines)
> As I understand it only the guix build command has an option to log output
> to a file.

Actually, the output of “guix build” 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
…
# 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
B
B
Brenton Horne wrote on 25 May 2017 22:33
(address . 27067@debbugs.gnu.org)
CANb+58JqyVBOB0U=1cBcXUm=Y6F+xHh0Yu_iDcbLzk0xpWhN7A@mail.gmail.com
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 <rekado@elephly.net> wrote:

Toggle quote (31 lines)
>
> Brenton Horne <brentonhorne77@gmail.com> writes:
>
> > As I understand it only the guix build command has an option to log
> output
> > to a file.
>
> Actually, the output of “guix build” 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
> …
> # 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
>
>


--
Thanks for your time,
Brenton
Attachment: file
R
R
Ricardo Wurmus wrote on 25 May 2017 23:30
(name . Brenton Horne)(address . brentonhorne77@gmail.com)(address . 27067@debbugs.gnu.org)
87fufsvd3o.fsf@elephly.net
Brenton Horne <brentonhorne77@gmail.com> writes:

Toggle quote (6 lines)
> 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
L
L
Ludovic Courtès wrote on 30 May 2017 22:14
(name . Brenton Horne)(address . brentonhorne77@gmail.com)(address . 27067@debbugs.gnu.org)
87k24yf6fo.fsf@gnu.org
Hi Brenton,

Brenton Horne <brentonhorne77@gmail.com> skribis:

Toggle quote (2 lines)
> As I understand it only the guix build command has an option to log output to a file.

Every derivation that is built, regardless of the command, has its log
stored in /var/log/guix/drvs. What ‘guix build’ has is a simple way to
get the file name or URL of a build log:

guix build --log-file coreutils

See:

(specifically --lose-logs and --disable-log-compression)

Can we say your feature request has already been fulfilled? :-)

Thanks,
Ludo’.
S
S
swedebugia wrote on 17 Dec 2018 10:30
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
(address . 27067@debbugs.gnu.org)
89638742053c32cc476eee3659f23131@riseup.net
Hi

I think the current logging is good enough.

I vote for closing this as Brenton did not answer during a long time and
nobody else thought this was worth implementing.

We could add a note to the manual with a very general pipe output tip,
but it would probably just clutter an already large manual.

--
Cheers
Swedebugia
L
L
Ludovic Courtès wrote on 18 Dec 2018 12:21
(address . swedebugia@riseup.net)(address . 27067-done@debbugs.gnu.org)
87tvjbgjvv.fsf@gnu.org
Hi,

swedebugia@riseup.net skribis:

Toggle quote (5 lines)
> I think the current logging is good enough.
>
> I vote for closing this as Brenton did not answer during a long time and
> nobody else thought this was worth implementing.

I agree, done!

Ludo’.
Closed
?