From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#32895: file progress reporter crashes on small files
Date: Wed, 03 Oct 2018 23:08:54 +0200
Message-ID: <87a7nuloux.fsf@gnu.org>
References: <idj7ej121mo.fsf@bimsb-sys02.mdc-berlin.net>
	<8736too7bp.fsf@gnu.org> <871s98v2yr.fsf@mdc-berlin.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41972)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1g7oPD-0005cf-79
	for bug-guix@gnu.org; Wed, 03 Oct 2018 17:10:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1g7oPC-0001ec-FX
	for bug-guix@gnu.org; Wed, 03 Oct 2018 17:10:03 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:60130)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1g7oPC-0001eI-1A
	for bug-guix@gnu.org; Wed, 03 Oct 2018 17:10:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1g7oPB-000743-OV
	for bug-guix@gnu.org; Wed, 03 Oct 2018 17:10:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.32895.B32895.153860096527099@debbugs.gnu.org>
In-Reply-To: <871s98v2yr.fsf@mdc-berlin.de> (Ricardo Wurmus's message of "Tue,
	2 Oct 2018 16:27:08 +0200")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 32895@debbugs.gnu.org

Hello,

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> Ludovic Court=C3=A8s <ludo@gnu.org> writes:
>
>> Hello,
>>
>> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> 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 emitti=
ng an
>> incorrect build trace.
>>
>> Do you have the exact command to reproduce it?
>
> Unfortunately, I don=E2=80=99t.

Or do you have the log around?  If you run, say:

  grep -r "download-progress .*#f" /var/log/guix/drvs

?

Looking at the code, I think only =E2=80=98progress-reporter/trace=E2=80=99=
 emits those
traces and only through calls to =E2=80=98dump-port*=E2=80=99, and I don=E2=
=80=99t see where
this #f could come from.

TIA,
Ludo=E2=80=99.