From: Parnikkapore <poomklao@yahoo.com>
To: help-guix@gnu.org
Subject: Cuirass remote worker is stuck building with 1 core
Date: Mon, 09 Oct 2023 09:14:25 +0800 [thread overview]
Message-ID: <c85eeaad7cb0c2698e5b1e6edd6f3df6eadb94c7.camel@yahoo.com> (raw)
In-Reply-To: c85eeaad7cb0c2698e5b1e6edd6f3df6eadb94c7.camel.ref@yahoo.com
I noticed that the Cuirass remote worker in my channel-building VM only builds things with 1 core, despite me having configured Guix to use multiple cores per build.
# Reproduction instructions
On a multi-core QEMU VM running Guix System with a Cuirass setup, run the following command:
```
cuirass remote-worker -w 1
```
This will result in the message "starting 1 workers (parallelism: 1 cores)".
# Expected output
The remote worker tries to build with the number of cores specified in guix-daemon's --cores. That, or $(nproc).
It should be noted that my bare-metal foreign distro install correctly selects $(nproc)-core parallelism. However, I have created multiple QEMU VMs running Guix System, and they all reproduce this bug.
# Appendix
## channels.scm
```
(list (channel
(name 'guix)
(url "https://git.savannah.gnu.org/git/guix.git")
(branch "master")
(commit
"577fd21122ca50ab7594be9adf0c5c06d5b26678")
(introduction
(make-channel-introduction
"9edb3f66fd807b096b48283debdcddccfea34bad"
(openpgp-fingerprint
"BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA")))))
```
## repro script
```
cd "$(dirname "$0")" | exit
guix time-machine -C ./channels.scm -- shell cuirass -- sh -c 'sudo $(which cuirass) remote-server --no-publish -c /tmp/cuirass-cache & sudo $(which cuirass) remote-worker -w 1'
```
next parent reply other threads:[~2023-10-09 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c85eeaad7cb0c2698e5b1e6edd6f3df6eadb94c7.camel.ref@yahoo.com>
2023-10-09 1:14 ` Parnikkapore [this message]
2023-10-09 15:01 ` Cuirass remote worker is stuck building with 1 core Parnikkapore
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=c85eeaad7cb0c2698e5b1e6edd6f3df6eadb94c7.camel@yahoo.com \
--to=poomklao@yahoo.com \
--cc=help-guix@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.
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).