[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#32895: file progress reporter crashes on small files

From: Ludovic Courtès
Subject: bug#32895: file progress reporter crashes on small files
Date: Thu, 04 Oct 2018 10:31:07 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)


address@hidden (Ludovic Courtès) skribis:

> Ricardo Wurmus <address@hidden> skribis:
>> Ludovic Courtès <address@hidden> writes:
>>> Hello,
>>> Ricardo Wurmus <address@hidden> skribis:
>>>> guix/progress.scm:214:25: In procedure display-download-progress:
>>>> In procedure /: Wrong type argument in position 1: #f
>>>> This happens because “transferred” in the “else” 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
>>>> “print-build-event”.
>>> Indeed, that seems to be the case.  This would mean we’re emitting an
>>> incorrect build trace.
>>> Do you have the exact command to reproduce it?
>> Unfortunately, I don’t.
> Or do you have the log around?  If you run, say:
>   grep -r "download-progress .*#f" /var/log/guix/drvs
> ?

Turns out I stumbled upon this bug by change.  The traces I was getting

--8<---------------cut here---------------start------------->8---
@ download-progress 
https://codeload.github.com/opencv/opencv_extra/zip/3.4.3 - 472383488
@ download-progress 
https://codeload.github.com/opencv/opencv_extra/zip/3.4.3 - 478478336
@ download-progress 
https://codeload.github.com/opencv/opencv_extra/zip/3.4.3 - 484704256
@ download-progress 
https://codeload.github.com/opencv/opencv_extra/zip/3.4.3 - #f
@ download-succeeded 
https://codeload.github.com/opencv/opencv_extra/zip/3.4.3 487641438
--8<---------------cut here---------------end--------------->8---

The next-to-last one was incorrect.

This is fixed in 1d0be47ab680db938ac8da1ee65e1de91e198f67.  I’ll push an
update of the ‘guix’ package so we get an updated daemon with the fix
(for the “builtin:download” derivations.)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]