From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ngillmann@runbox.com>
Cc: 24496@debbugs.gnu.org
Subject: bug#24496: offloading should fall back to local build after n tries
Date: Mon, 26 Sep 2016 18:20:51 +0900 [thread overview]
Message-ID: <87r387nhjg.fsf@gnu.org> (raw)
In-Reply-To: <8760ppr3q3.fsf@we.make.ritual.n0.is> (ng0's message of "Wed, 21 Sep 2016 09:39:48 +0000")
Hello!
ng0 <ngillmann@runbox.com> skribis:
> When I forgot that my build machine is offline and I did not pass
> --no-build-hook, the offloading keeps trying forever until I had to
> cancel the build, boot the build-machine and started the build again.
>
> A solution could be a config option or default behavior which after
> failing to offload for n times gives up and uses the local builder.
>
> Is this desired at all? Setups like hydra could get problems, but for
> small setups with the same architecture there could be a solution beyond
> --no-build-hook?
Like you say, on Hydra-style setup this could be a problem: the
front-end machine may have --max-jobs=0, meaning that it cannot perform
builds on its own.
So I guess we would need a command-line option to select a different
behavior. I’m not sure how to do that because ‘guix offload’ is
“hidden” behind ‘guix-daemon’, so there’s no obvious place for such an
option.
In the meantime, you could also hack up your machines.scm: it would
return a list where unreachable machines have been filtered out.
Ludo’.
next prev parent reply other threads:[~2016-09-26 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 9:39 bug#24496: offloading should fall back to local build after n tries ng0
2016-09-26 9:20 ` Ludovic Courtès [this message]
2016-10-04 17:08 ` ng0
2016-10-05 11:36 ` Ludovic Courtès
2021-12-16 12:52 ` zimoun
2021-12-17 15:33 ` Ludovic Courtès
2021-12-17 21:57 ` Maxim Cournoyer
2021-12-18 0:10 ` zimoun
2021-12-21 14:28 ` Ludovic Courtès
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=87r387nhjg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=24496@debbugs.gnu.org \
--cc=ngillmann@runbox.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).