all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 33378@debbugs.gnu.org
Subject: bug#33378: offload: Avoid hosts with little or no free disk space
Date: Sun, 23 Dec 2018 12:20:17 -0500	[thread overview]
Message-ID: <8736qoi2hf.fsf@netris.org> (raw)
In-Reply-To: <87r2ealci0.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 21 Dec 2018 23:51:35 +0100")

Hi Ludovic,

Ludovic Courtès <ludo@gnu.org> writes:

> ludo@gnu.org (Ludovic Courtès) skribis:
>
>> ‘choose-build-machine’ in (guix scripts offload) could/should exclude
>> build machines that don’t have at least, say, 100 MiB available in their
>> store.  That would avoid ENOSPC build failures such as
>> <https://berlin.guixsd.org/log/0hvhrfdjwnmdm2rdf58knshbbikm4ryv-r-bsgenome-hsapiens-ucsc-hg19-masked-1.3.99>.
>
> Done in commit 63b0c3eaccdf1816b419632cd7fe721934d2eb27.

Many builds require more free space than 100 MB, so this is only a
partial solution.  Also, if multiple builds are happening on the same
machine, the amount of free space available for each build will be less
than 100 MB.

Finally, the other related commit that attempts to detect build failures
caused by ENOSPC by checking if there's at least 10 MB free after the
failure won't often work in practice, I suspect.  The problem is, by the
time you perform that check, the build directory has already been
deleted.

       Mark

  reply	other threads:[~2018-12-23 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14 13:50 bug#33378: offload: Avoid hosts with little or no free disk space Ludovic Courtès
2018-12-21 22:51 ` Ludovic Courtès
2018-12-23 17:20   ` Mark H Weaver [this message]
2018-12-23 20:58     ` Ludovic Courtès
2018-12-24 18:45       ` Mark H Weaver

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=8736qoi2hf.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=33378@debbugs.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.
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.