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:06:51 +0000 Message-ID: <20180309140651.flyiu2chdnmjnbno@abyayala> References: <20180309091549.lris2yvh3uh65and@abyayala> <878tb1l5k7.fsf@elephly.net> 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]:55538) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1euIfo-0002jg-CM for guix-devel@gnu.org; Fri, 09 Mar 2018 09:07:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1euIfj-0007l0-Dt for guix-devel@gnu.org; Fri, 09 Mar 2018 09:07:04 -0500 Received: from aibo.runbox.com ([91.220.196.211]:55578) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1euIfj-0007kF-76 for guix-devel@gnu.org; Fri, 09 Mar 2018 09:06:59 -0500 Content-Disposition: inline In-Reply-To: <878tb1l5k7.fsf@elephly.net> 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: Ricardo Wurmus Cc: guix-devel@gnu.org, ng0 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. -- A88C8ADD129828D7EAC02E52E22F9BBFEE348588 https://n0.is/~ng0