From: Mark H Weaver <mhw@netris.org>
To: 19806@debbugs.gnu.org
Subject: bug#19806: substitute-binary --query busy for 36 minutes with no output
Date: Sat, 07 Feb 2015 13:14:31 -0500 [thread overview]
Message-ID: <87d25l37y0.fsf@netris.org> (raw)
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:
--8<---------------cut here---------------start------------->8---
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>
--8<---------------cut here---------------end--------------->8---
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
reply other threads:[~2015-02-07 18:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d25l37y0.fsf@netris.org \
--to=mhw@netris.org \
--cc=19806@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.