unofficial mirror of 
 help / color / mirror / Atom feed
From: Parnikkapore <>
Subject: Cuirass remote worker is stuck building with 1 core
Date: Mon, 09 Oct 2023 09:14:25 +0800	[thread overview]
Message-ID: <> (raw)

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 "")
        (branch "master")
              "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'

       reply	other threads:[~2023-10-09 10:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).