From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: how to get the path of the logfile after an unsuccesful build? Date: Fri, 9 Mar 2018 14:39:34 +0000 Message-ID: <20180309143934.4cuuzjsopjvlfvlg@abyayala> References: <20180309091549.lris2yvh3uh65and@abyayala> <878tb1l5k7.fsf@elephly.net> <20180309140651.flyiu2chdnmjnbno@abyayala> <87vae5iarb.fsf@lassieur.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34204) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1euJBJ-0002HP-Kh for guix-devel@gnu.org; Fri, 09 Mar 2018 09:39:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1euJBG-0003ky-GJ for guix-devel@gnu.org; Fri, 09 Mar 2018 09:39:37 -0500 Received: from aibo.runbox.com ([91.220.196.211]:58602) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1euJBG-0003ka-8u for guix-devel@gnu.org; Fri, 09 Mar 2018 09:39:34 -0500 Content-Disposition: inline In-Reply-To: <87vae5iarb.fsf@lassieur.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?utf-8?Q?Cl=C3=A9ment?= Lassieur Cc: guix-devel@gnu.org, ng0 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 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