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

l...@gnu.org (Ludovic Courtès) writes: > Hartmut Goebel skribis: > >> Am 09.03.2018 um 15:06 schrieb ng0: >>> The daemon doesn’t keep logs for failed builds. >> >> I asked this a few month ago and was told this is a bug. > > It does keep build logs even for aborted

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

Mark H Weaver writes: > ng0 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

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

Catonano writes: > Look, there's a manual page about that ! > > https://www.gnu.org/software/guix/manual/html_node/Debugging-Build-Failures.html#Debugging-Build-Failures > > Are we talking about the same thing ? There is “guix build --log-file” (see the previous manual

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

Catonano transcribed 1.7K bytes: > 2018-03-09 10:15 GMT+01:00 ng0 : > > > Hi, > > > > 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

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

2018-03-11 7:28 GMT+01:00 Catonano : > > > 2018-03-09 10:15 GMT+01:00 ng0 : > >> Hi, >> >> 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

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

2018-03-09 10:15 GMT+01:00 ng0 : > Hi, > > 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 >

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

Ludovic Courtès writes: > Hartmut Goebel skribis: > >> Am 09.03.2018 um 15:06 schrieb ng0: >>> The daemon doesn’t keep logs for failed builds. >> >> I asked this a few month ago and was told this is a bug. > > It does keep build logs even for aborted

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

Hartmut Goebel skribis: > Am 09.03.2018 um 15:06 schrieb ng0: >> The daemon doesn’t keep logs for failed builds. > > I asked this a few month ago and was told this is a bug. It does keep build logs even for aborted and failed builds. If you have evidence that it

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

ng0 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

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

ng0 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. Why won't

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

Hartmut Goebel writes: > Am 09.03.2018 um 15:06 schrieb ng0: >> The daemon doesn’t keep logs for failed builds. > > I asked this a few month ago and was told this is a bug. I think it would be great to create a bug report.

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

Hartmut Goebel transcribed 332 bytes: > Am 09.03.2018 um 15:06 schrieb ng0: > > The daemon doesn’t keep logs for failed builds. > > I asked this a few month ago and was told this is a bug. > > -- > Regards > Hartmut Goebel > > | Hartmut Goebel | h.goe...@crazy-compilers.com

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

Am 09.03.2018 um 15:06 schrieb ng0: > The daemon doesn’t keep logs for failed builds. I asked this a few month ago and was told this is a bug. -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you

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

Clément Lassieur transcribed 766 bytes: > ng0 writes: > > > Ricardo Wurmus transcribed 358 bytes: > >> > >> ng0 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

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

ng0 writes: > Ricardo Wurmus transcribed 358 bytes: >> >> ng0 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,

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

Ricardo Wurmus transcribed 358 bytes: > > ng0 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

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

Hi, 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. -- A88C8ADD129828D7EAC02E52E22F9BBFEE348588