all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 33378@debbugs.gnu.org
Subject: bug#33378: offload: Avoid hosts with little or no free disk space
Date: Mon, 24 Dec 2018 13:45:08 -0500	[thread overview]
Message-ID: <875zviyd9s.fsf@netris.org> (raw)
In-Reply-To: <87k1k0gdti.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 23 Dec 2018 21:58:49 +0100")

Hi Ludovic,

Ludovic Courtès <ludo@gnu.org> writes:
> I suppose the only way to solve this correctly would be to keep the
> build tree and then delete it from (guix scripts offload).  WDYT?

Generally, this sounds like a reasonable approach.  However, one issue
is that it will likely lead to build directories being left around
occasionally when transient network outages occur.  Those would need to
be cleaned up manually, or by cron jobs on the build slaves.

Also, does the daemon API provide a way to find the name of the build
directory?  What if there's more than one build directory with the same
name and version number, differing only by the numeric suffix?

Ideally, there would be a way for the build-side code to return a result
code indicating that the build "aborted" rather than "failed", for this
to be recognized by the daemon as a transient failure (i.e. not cached),
and to propagate this information back to the client who requested the
build.  Do the relevant daemon APIs and offloading protocols allow for
this information to be propagated to the client?

       Thanks,
         Mark

      reply	other threads:[~2018-12-24 18:47 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
2018-12-23 20:58     ` Ludovic Courtès
2018-12-24 18:45       ` Mark H Weaver [this message]

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=875zviyd9s.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=33378@debbugs.gnu.org \
    --cc=ludo@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.