From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#32895: file progress reporter crashes on small files Date: Tue, 2 Oct 2018 16:27:08 +0200 Message-ID: <871s98v2yr.fsf@mdc-berlin.de> References: <8736too7bp.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]:46813) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g7Lmm-0005JH-LO for bug-guix@gnu.org; Tue, 02 Oct 2018 10:36:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g7Led-0004gQ-Db for bug-guix@gnu.org; Tue, 02 Oct 2018 10:28:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58361) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g7Led-0004gG-9N for bug-guix@gnu.org; Tue, 02 Oct 2018 10:28:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g7Lec-0007dz-I4 for bug-guix@gnu.org; Tue, 02 Oct 2018 10:28:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <8736too7bp.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 32895@debbugs.gnu.org Ludovic Court=C3=A8s writes: > Hello, > > Ricardo Wurmus skribis: > >> guix/progress.scm:214:25: In procedure display-download-progress: >> In procedure /: Wrong type argument in position 1: #f >> >> This happens because =E2=80=9Ctransferred=E2=80=9D in the =E2=80=9Celse= =E2=80=9D branch of (@ (guix >> progress) display-download-progress) is #f instead of a number. This >> could be the result of running string->number on an invalid string in >> =E2=80=9Cprint-build-event=E2=80=9D. > > Indeed, that seems to be the case. This would mean we=E2=80=99re emittin= g an > incorrect build trace. > > Do you have the exact command to reproduce it? Unfortunately, I don=E2=80=99t. It=E2=80=99s hard to reproduce this when a= ll these cabal revisions have already been downloaded. This also depends a lot on the actual download speed. I only got this for cabal revisions, so locally building any of the ghc-* packages with #:cabal-revision arguments might be sufficient to trigger the bug. -- Ricardo