From: Saku Laesvuori <saku@laesvuori.fi>
To: Aleksandr Vityazev <avityazew@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: guix offload
Date: Wed, 20 Dec 2023 17:19:42 +0200 [thread overview]
Message-ID: <a6dzcvchjmrskokvsmwfy3257ojhbao3me4pilnxijy3pkc5tk@cjyvyzvqm6y6> (raw)
In-Reply-To: <87o7el9lx8.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
> Hello.
>
> I have a configured build machine. From time to time it is not available
> and guix build gets stuck in an endless loop of:
>
> guix offload: error: failed to connect to : No route to host
> process 13902 acquired build slot
> guix offload: error: failed to connect to : No route to host
> process 13902 acquired build slot
>
> Is it possible to make the build continue locally after several
> unsuccessful attempts?
I don't think that is currently possible. You can, however, filter your
build machines with a snippet like this in the operating system
declaration[1]. This filters away hosts that are not resolvable, but you
could adapt it to use some other predicate if needed.
```
(build-machines
(list #~(let* ((resolvable? (lambda (machine)
(false-if-exception
(gethost (build-machine-name machine))))))
(filter resolvable?
(list (build-machine
(name "example.com")
(systems '("x86_64-linux"))
(host-key "xxxx")
(user "offload")))))))
```
If you don't use guix system you can implement the filter logic in
/etc/guix/machines.scm.
[1]: https://guix.gnu.org/manual/devel/en/guix.html#guix_002dconfiguration_002dbuild_002dmachines
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-20 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 11:02 guix offload Aleksandr Vityazev
2023-12-20 12:29 ` Reza Housseini
2023-12-20 13:08 ` Aleksandr Vityazev
2023-12-20 15:19 ` Saku Laesvuori [this message]
2023-12-20 16:29 ` Aleksandr Vityazev
2024-02-15 16:23 ` Simon Tournier
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=a6dzcvchjmrskokvsmwfy3257ojhbao3me4pilnxijy3pkc5tk@cjyvyzvqm6y6 \
--to=saku@laesvuori.fi \
--cc=avityazew@gmail.com \
--cc=help-guix@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.
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).