From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Andy Wingo <wingo@igalia.com>, help-guix@gnu.org, 27476@debbugs.gnu.org
Subject: bug#27476: guix pull fails on powerful server
Date: Sat, 07 Oct 2017 17:11:42 +0200 [thread overview]
Message-ID: <87po9zj8lt.fsf__37888.926981441$1507389132$gmane$org@gnu.org> (raw)
In-Reply-To: <87shf44ny0.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 30 Sep 2017 09:59:03 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> I’ve tried “guix pull” on the same server again, this time limiting CPUs
> with “taskset -c 0 guix pull”:
As a stopgap, commit aba219af0fed6a349af930f19c913fb87e6a69dd ensures
that ‘--cores’ is honored. So if you run “guix pull --cores=1”, it will
build things sequentially.
Now, to take advantage of that, you first need to update to the current
Guix…
Ludo’.
next prev parent reply other threads:[~2017-10-07 15:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h8vvp1q7.fsf@elephly.net>
2017-09-22 14:10 ` bug#27476: guix pull fails on powerful server Ludovic Courtès
2017-09-25 7:27 ` Andy Wingo
2017-09-25 13:03 ` Ludovic Courtès
[not found] ` <87a81jj5gg.fsf@gnu.org>
2017-09-25 14:02 ` Ricardo Wurmus
2017-09-30 7:59 ` Ricardo Wurmus
[not found] ` <87shf44ny0.fsf@elephly.net>
2017-10-03 20:29 ` Marius Bakke
[not found] ` <87a818dlgz.fsf@fastmail.com>
2017-10-04 13:15 ` Ricardo Wurmus
2017-10-04 15:09 ` Clément Lassieur
[not found] ` <87o9pnt0ei.fsf@lassieur.org>
2017-10-04 16:17 ` Ricardo Wurmus
2017-10-07 15:11 ` Ludovic Courtès [this message]
[not found] ` <87po9zj8lt.fsf@gnu.org>
2017-10-10 7:17 ` Ricardo Wurmus
[not found] ` <878tgjmpz6.fsf@elephly.net>
2017-10-10 11:32 ` Ludovic Courtès
2017-10-12 13:37 ` Ludovic Courtès
[not found] ` <877ew0o5br.fsf@gnu.org>
2017-10-13 20:29 ` Ricardo Wurmus
2017-10-13 21:04 ` Ricardo Wurmus
2017-10-13 21:10 ` Ricardo Wurmus
2017-11-07 10:57 ` Ludovic Courtès
[not found] ` <878tfi9x15.fsf@gnu.org>
2018-04-30 21:19 ` Ludovic Courtès
2018-04-30 21:39 ` bug#27476: libguile/memoize.c is not thread safe, so syntax parameter expansion is not thread-safe Ludovic Courtès
2018-05-09 8:41 ` Andy Wingo
2018-05-09 9:23 ` Ludovic Courtès
2018-05-09 10:18 ` Andy Wingo
2019-02-06 14:48 ` Ludovic Courtès
2019-02-06 16:14 ` Andy Wingo
2019-02-06 22:09 ` Ludovic Courtès
2019-01-29 10:07 ` bug#27476: guix pull fails on powerful server Ricardo Wurmus
2017-09-25 8:43 ` Clément Lassieur
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='87po9zj8lt.fsf__37888.926981441$1507389132$gmane$org@gnu.org' \
--to=ludo@gnu.org \
--cc=27476@debbugs.gnu.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
--cc=wingo@igalia.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).