substitute-binary --query busy for 36 minutes with no output

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Mark H Weaver
Owner
unassigned
Submitted by
Mark H Weaver
Severity
normal

Debbugs page

M
M
Mark H Weaver wrote on 7 Feb 2015 10:14
(address . bug-guix@gnu.org)
87d25l37y0.fsf@netris.org
While updating my profile with "guix package -c1 -u", "substitute-binary
--query" hung for 36 minutes with ~90% CPU utilization without any
active network connections and without printing any output. Here was
the relevant excerpt from 'ps auxwwf' after about 30 minutes of CPU
time:

Toggle snippet (8 lines)
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
[...]
root 23061 0.0 0.0 5804 1248 ? Ss 12:29 0:00 /gnu/store/538qidv49w2v942502yqmv0fz187xd9z-guix-0.8.1.f1082ec/bin/guix-daemon --build-users-group guixbuild --cores=1 --max-jobs=1
root 23087 33.3 0.2 10384 4444 ? Ss 12:30 11:44 \_ /gnu/store/538qidv49w2v942502yqmv0fz187xd9z-guix-0.8.1.f1082ec/bin/guix-daemon 23079 guixbuild --cores=1 --max-jobs=1
root 23120 87.9 58.2 1294632 1198688 ? Sl 12:30 30:25 \_ /gnu/store/122jv790mv2mlnylbrbzav65vghbw93n-guile-2.0.11/bin/guile --no-auto-compile /gnu/store/538qidv49w2v942502yqmv0fz187xd9z-guix-0.8.1.f1082ec/bin/guix substitute-binary --query
root 23211 0.0 0.0 0 0 ? Zs 12:30 0:00 \_ [guix] <defunct>

Looking at the nginx logs on hydra, I see that it downloaded a single
nar file (for paredit) very soon after starting up, and then didn't
download anything else from hydra until ~36 minutes later, when it
downloaded /nix-cache-info and then a narinfo file. It then proceeded
to do several grafting operations locally.

The 'guix package' command I'm running is v0.8.1-90-g710f3ce, and the
'guix-daemon' and substitute binary is guix-0.8.1.f1082ec.

Any ideas what it was doing during those 36 silent minutes?

Mark
L
L
Ludovic Courtès wrote on 24 Aug 2019 06:37
control message for bug #19806
(address . control@debbugs.gnu.org)
87zhjywup5.fsf@gnu.org
tags 19806 unreproducible
close 19806
quit
?
Your comment

This issue is archived.

To comment on this conversation send an email to 19806@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 19806
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch