all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 30644@debbugs.gnu.org
Subject: bug#30644: Cuirass runs out of build users
Date: Mon, 5 Mar 2018 10:02:56 +0100	[thread overview]
Message-ID: <20180305090256.GA9171@jurong> (raw)
In-Reply-To: <20180302140833.GB3213@macbook41>

On Fri, Mar 02, 2018 at 04:08:33PM +0200, Efraim Flashner wrote:
> When I use a shell script to build all the packages, if a package hangs
> and gets eaten by the timout-limit then it holds the build user and
> space in /tmp until all 10 builders are taken and building stops or all
> the builds finish and then it releases them.

Right now, I observe something else: Only one package is built at a time,
taking space in /tmp. But it is not the same build user; I saw one package
with guixbuilder06, and now it is building one package with guixbuilder01.

Is there a way to check which builders are considered taken? A lock file
somewhere?

Andreas

  reply	other threads:[~2018-03-05  9:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28  9:07 bug#30644: Cuirass runs out of build users Andreas Enge
2018-03-01 14:01 ` Ludovic Courtès
2018-03-01 20:35   ` Andreas Enge
2018-03-02 14:08 ` Efraim Flashner
2018-03-05  9:02   ` Andreas Enge [this message]
2018-03-05 15:53     ` Andreas Enge
2018-03-05 19:55       ` Andreas Enge
2018-03-07 22:35       ` Ludovic Courtès
2018-03-07 23:01         ` Danny Milosavljevic
2018-03-08  0:25           ` Danny Milosavljevic
2018-03-08  0:29             ` Danny Milosavljevic
2018-03-08 12:01               ` Ludovic Courtès
2018-03-11  6:06                 ` Danny Milosavljevic
2018-03-11 21:43                   ` Ludovic Courtès
2018-03-24 13:15                     ` Danny Milosavljevic
2018-03-25 12:40                       ` Ludovic Courtès
2021-03-25 13:17                     ` Mathieu Othacehe

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=20180305090256.GA9171@jurong \
    --to=andreas@enge.fr \
    --cc=30644@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    /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.