From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: how to get the path of the logfile after an unsuccesful build? Date: Fri, 23 Mar 2018 05:54:44 +0100 Message-ID: <87605nfl2j.fsf@gmail.com> References: <20180309091549.lris2yvh3uh65and@abyayala> <87po4c7wcl.fsf@netris.org> <87a7vejen7.fsf@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42792) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ezEj7-0003hV-Ag for guix-devel@gnu.org; Fri, 23 Mar 2018 00:54:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ezEj6-0006Xs-Ab for guix-devel@gnu.org; Fri, 23 Mar 2018 00:54:53 -0400 Received: from mail-pl0-x22b.google.com ([2607:f8b0:400e:c01::22b]:35371) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ezEj6-0006Xk-3v for guix-devel@gnu.org; Fri, 23 Mar 2018 00:54:52 -0400 Received: by mail-pl0-x22b.google.com with SMTP id p9-v6so6802729pls.2 for ; Thu, 22 Mar 2018 21:54:51 -0700 (PDT) In-Reply-To: <87a7vejen7.fsf@netris.org> (Mark H. Weaver's message of "Sun, 11 Mar 2018 20:55:56 -0400") 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: Mark H Weaver Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Hartmut Goebel skribis: > >> Am 09.03.2018 um 15:06 schrieb ng0: >>> The daemon doesn=E2=80=99t 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 doesn=E2=80=99t, then please report it. :-) Can these be readily accessed via "guix build --log-file", or does one have to go spelunking in one's file system to find them? Mark H Weaver writes: > Then it corresponds to a grafted derivation, and you need to find the > original ungrafted derivation. In most cases this can be done by > running "guix build --log-file /gnu/store/=E2=80=A6-foo", passing the fir= st file > name from the "grafting" message. > > Alternatively, you could look in the .drv file of the grafting > derivation, which will include the file name of the original ungrafted > derivation among its input derivations. In this case, you can actually just add --no-grafts to the invocation, as in: guix build --no-grafts --log-file guile This will show you the log of the build, before applying any grafts. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlq0iJQACgkQ3UCaFdgi Rp08mg/9G6V38aqhhEQoyqGwpJ9qGhBIjBjROCBDl5xCacZrsyLYWl1JKp/3Uxey eOxRhDtp59QpKocDfq3UjAH9UkhiSuLzPcgN1DVrrdpxHNxZ8orgN64GO24Mqibi xIIQxx8V3FIIzsZYbeS8SP2luvrcdiaXWJkRUcrW3URpdvYrGYVFQeIIiaD3acqI o4EDtw0rilpvzyKuXYR5g0enQPvubiSe5NpOh8JiBUUC2uhx/SCyzaxxsqmgjDQi Pg5P/t+9V8wzgKxpobO/K2Sj0fF138V/pGPkF0lEaOQYXGSzUxAGqOipvACCzT9c 7pNs/GM9e7QRcHdDlJc4LBkyHySN8N/W+UQcrJyleF72hKBMM+Rqv5lGC1qSzDu6 9Mj/HOiqiopbE5Dlx7AgALk7TO3cS3qw6NliMP3sMXdNtAGlnFrvT2Cvqpggg91y at6RpHFMisVFzovoEHwIreqXnsolWk+9058NlHPONGyCAS+HBkRhkwQQ8n+mIgM3 ak8n/1fbTfRFfO45VzfjpPppJmlZbOgv5p9suv8BXVE7rQkUpUuQ7ViG2nm5/Gen RBMHVd1p7XjLvlOcAXeG1SYSwzjSj0Ssc7vDmQxQwtOSnFg+Bfkhpc98IgIf9Xdd 0BZgAUxBy/FT3hsC++gldpfkbvoFzDTsArpG4w/1hWmsp265urM= =9E2j -----END PGP SIGNATURE----- --=-=-=--