From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?Q?Cl=C3=A9ment?= Lassieur <clement@lassieur.org>
Subject: Re: how to get the path of the logfile after an unsuccesful build?
Date: Fri, 09 Mar 2018 15:28:24 +0100
Message-ID: <87vae5iarb.fsf@lassieur.org>
References: <20180309091549.lris2yvh3uh65and@abyayala>
	<878tb1l5k7.fsf@elephly.net>
	<20180309140651.flyiu2chdnmjnbno@abyayala>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59389)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <clement@lassieur.org>) id 1euJ0b-0002Yc-4P
	for guix-devel@gnu.org; Fri, 09 Mar 2018 09:28:34 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <clement@lassieur.org>) id 1euJ0X-0007tA-7B
	for guix-devel@gnu.org; Fri, 09 Mar 2018 09:28:33 -0500
Received: from mail.lassieur.org ([83.152.10.219]:53678)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <clement@lassieur.org>)
	id 1euJ0W-0007s1-SF
	for guix-devel@gnu.org; Fri, 09 Mar 2018 09:28:29 -0500
In-reply-to: <20180309140651.flyiu2chdnmjnbno@abyayala>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: ng0 <ng0@n0.is>
Cc: guix-devel@gnu.org

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?