From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Guix build output insufficient Date: Wed, 12 Sep 2018 19:25:11 +0200 Message-ID: <87k1nqk4qw.fsf@elephly.net> References: <20180911082653.27gmposcatilbsuq@thebird.nl> <875zzcl09b.fsf@elephly.net> <87sh2e7ics.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38927) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g08tP-0003cf-38 for guix-devel@gnu.org; Wed, 12 Sep 2018 13:25:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g08tN-0003kV-83 for guix-devel@gnu.org; Wed, 12 Sep 2018 13:25:31 -0400 In-reply-to: <87sh2e7ics.fsf@gnu.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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel Hi, > What about immediately giving the file name of the log, as with the > patch attached? Several people have already mentioned not knowing about > =E2=80=98guix build --log-file=E2=80=99 so this would probably be helpful. This would be fine. Note that the patch cannot be applied because I had to change how =E2=80=9C@ build-failed=E2=80=9D is treated. The underlying problem here is that the daemon may send a multi-line message through the port, which unfortunately doesn=E2=80=99t necessarily arrive in one piece. AFAICS the only such message is the hash mismatch error. If we could force it to remain on one line we could better format that single-line string in guix/ui.scm. (Now we get half of the message, followed by another string matching =E2=80=9C^\s+actual:\s+(.*)=E2=80=9D, which we cannot process as we do not = keep track of state.) -- Ricardo