From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#36684: "View build log" - but it's empty (at first)! Date: Wed, 17 Jul 2019 21:57:29 +0200 Message-ID: <877e8ga0ye.fsf@gnu.org> References: <87blxu1ny5.fsf@gmail.com> <877e8i1nnm.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:56025) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnq3v-0000gw-07 for bug-guix@gnu.org; Wed, 17 Jul 2019 15:58:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hnq3u-0002sB-2w for bug-guix@gnu.org; Wed, 17 Jul 2019 15:58:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:44233) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hnq3t-0002s1-VS for bug-guix@gnu.org; Wed, 17 Jul 2019 15:58:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hnq3t-000674-Rt for bug-guix@gnu.org; Wed, 17 Jul 2019 15:58:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <877e8i1nnm.fsf@gmail.com> (Chris Marusich's message of "Mon, 15 Jul 2019 23:47:25 -0700") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Chris Marusich Cc: 36684@debbugs.gnu.org Hi Chris, Chris Marusich skribis: > Whoops, I got my wires crossed. Those build logs are for > evolution-data-server, not ant-bootstrap. However, the same problem > holds for evolution-data-server - I built it, it failed, it said I could > find the logs at > /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9ni-evolution-data-serve= r-3.30.2.drv.bz2, > it was empty at first, but then it became full. I guess there=E2=80=99s a small window during which the bzip file handle ha= sn=E2=80=99t been closed, and so you could see an empty file. However, that window should be extremely small: as soon as the client disconnects or the build terminates, the daemon closes the log. > In fact, it is only partially full, since the file ends unexpectedly: > > $ bzcat /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9ni-evolution-da= ta-server-3.30.2.drv.bz2 > /dev/null > > bzcat: Compressed file ends unexpectedly; > perhaps it is corrupted? *Possible* reason follows. > bzcat: Success > Input file =3D /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9= ni-evolution-data-server-3.30.2.drv.bz2, output file =3D (stdout) > > It is possible that the compressed file(s) have become corrupted. > You can use the -tvv option to test integrity of such files. > > You can use the `bzip2recover' program to attempt to recover > data from undamaged sections of corrupted files. So this particular log file remained truncated? I=E2=80=99ve never experienced it. Is there a scenario that allows you to reproduce it? Thanks, Ludo=E2=80=99.