Re: how to get the path of the logfile after an unsuccesful build?

[ng0 <ng0@n0.is>]

Clément Lassieur transcribed 766 bytes:
> ng0 <ng0@n0.is> writes:
> 
> > Ricardo Wurmus transcribed 358 bytes:
> >> 
> >> ng0 <ng0@n0.is> writes:
> >> 
> >> > did we ever talk about that there's too little information on how to get
> >> > the current log file of a failed build? I need this right now (the full log)
> >> > and I can't remember how, and making use of the log folder in var/log/guix/ won't
> >> > help either.
> >> 
> >> The daemon doesn’t keep logs for failed builds.
> >> 
> >> -- 
> >> Ricardo
> >
> > So how are we supposed to figure out failures then that happen outside of the length of
> > the terminal scrollback? Of course I could run it in tmux, but having log files to
> > share of the failed build comes in handy when debugging builds with upstream/downstream
> > projects.
> 
> Can't you redirect the output to a file?

  guix build hello  2>&1 | tee output.txt

would work of course, but why throw away the logs when we could just save them?
It seems not very developer friendly to me. This way I will just write another
script that wraps around guix build and saves all my build logs to a location.
I think guix should handle this by default unless there are good reasons not to
do it.
-- 
A88C8ADD129828D7EAC02E52E22F9BBFEE348588
https://n0.is/~ng0