From: Leo Famulari <leo@famulari.name>
To: Marco van Hulten <marco@hulten.org>
Cc: help-guix@gnu.org
Subject: Re: successful installation, but problems updating
Date: Fri, 10 Nov 2017 11:35:39 -0500 [thread overview]
Message-ID: <20171110163539.GB11031@jasmine.lan> (raw)
In-Reply-To: <20171110082612.502198ae@jasniac.instanton>
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
On Fri, Nov 10, 2017 at 08:26:12AM +0100, Marco van Hulten wrote:
> kodi@watson ~$ time guix pull --cores=1
[...]
> compiling... 75.4% of 647 filesbuilding of `/gnu/store/gk5chb0dwpsq3na7b4gn1hd7h0h2b63h-guix-latest.drv' timed out after 3600 seconds of silence
[...]
> real 609m30.245s
> user 0m3.125s
> sys 0m0.875s
This is terrible, but you can work around it by passing a large value to
the --max-silent-time "common build option":
--max-silent-time=seconds
When the build or substitution process remains silent for more than seconds, terminate it and report a build failure.
https://www.gnu.org/software/guix/manual/html_node/Common-Build-Options.html
Out of curiosity, what kind of machine are you using? A full hour with
no output at all indicates that something is happening very slowly! Is
it swapping?
> - it took over 10 h to give me back control, whereas this used to be
> a bit over 2 h in previous tries;
Do you mean that the computer becomes unresponsive?
> What is Guix doing between 75.2 and 75.4 %?
I don't know exactly, but during `guix pull` Guix is built from source
with the Guile compiler.
There are some bugs in the current version of the Guile compiler that
cause it to require way more memory than expected. This is terrible on
memory-constrained systems because it forces the use of swap, which is
typically super slow. Hopefully we can deploy a fix soon.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-10 16:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 8:16 successful installation, but problems updating Marco van Hulten
2017-11-06 9:43 ` Carlo Zancanaro
2017-11-06 20:06 ` Marco van Hulten
2017-11-07 9:20 ` Ludovic Courtès
2017-11-07 10:58 ` Marco van Hulten
2017-11-08 1:37 ` Marco van Hulten
2017-11-09 7:45 ` Marco van Hulten
2017-11-09 13:19 ` Ludovic Courtès
2017-11-09 19:27 ` Marco van Hulten
2017-11-09 20:46 ` Marco van Hulten
2017-11-09 20:53 ` Mathieu Othacehe
2017-11-10 7:26 ` Marco van Hulten
2017-11-10 16:35 ` Leo Famulari [this message]
2017-11-11 22:23 ` Marco van Hulten
2017-11-12 1:26 ` Leo Famulari
2017-11-06 10:18 ` Thomas Sigurdsen
2017-11-10 5:58 ` Chris Marusich
2017-11-10 7:23 ` Carlo Zancanaro
2017-11-10 16:28 ` Leo Famulari
2017-11-10 23:30 ` Chris Marusich
2017-11-11 15:29 ` myglc2
2017-11-11 17:05 ` Chris Marusich
2017-11-11 18:06 ` myglc2
2017-11-12 1:29 ` Leo Famulari
2017-11-12 3:36 ` myglc2
2017-11-12 4:45 ` Leo Famulari
2017-11-12 11:10 ` Chris Marusich
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=20171110163539.GB11031@jasmine.lan \
--to=leo@famulari.name \
--cc=help-guix@gnu.org \
--cc=marco@hulten.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.