From: Tomas Volf <~@wolfsden.cz>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>,
guix-devel@gnu.org
Subject: Re: Should we document how to detect if build machines are reachable before trying to offload?
Date: Sun, 21 Jul 2024 19:25:46 +0200 [thread overview]
Message-ID: <Zp1EmsX6OA9zD2N1@ws> (raw)
In-Reply-To: <CAEwRq=pdDbiC9Oea9seQuEvb9goJqtAfrtm_wjS4cZWy36b_xg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On 2024-07-21 16:26:41 +0000, Vincent Legoll wrote:
> Hello,
>
> On Sun, Jul 21, 2024 at 12:57 PM Ludovic Courtès <ludo@gnu.org> wrote:
>
> > I guess this is probably what we should permit: building locally when we
> > cannot offload.
> >
> > Does that make sense?
> >
>
> What about making "build locally" not a special case, but just "offloading
> to
> localhost" ?
That will not work without reworking (fixing) the offload mechanism. (Some?)
flags are currently ignored for offload (--check, --rounds, ...), but you want
to have them working at least locally when you need them.
>
> Maybe as an implicit default, so that it would work naturally as today.
>
> And with some way to deny it for people who don't want to build locally
> at all, whatever their reason might be.
>
> Would that trim some "build locally"-specific code ?
>
> Is that already how it's done ?
>
> Is the idea crazy / dumb ?
No, I like it in general, if nothing else it would put the offload code on
critical path, ensuring it fully works.
I wonder what are the downsides (I am sure there are some).
>
> --
> Vincent Legoll
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-07-21 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 15:45 Should we document how to detect if build machines are reachable before trying to offload? Sergio Pastor Pérez
2024-07-11 9:48 ` Ludovic Courtès
2024-07-11 20:23 ` Sergio Pastor Pérez
2024-07-21 12:56 ` Ludovic Courtès
2024-07-21 15:59 ` Sergio Pastor Pérez
2024-07-21 16:26 ` Vincent Legoll
2024-07-21 17:25 ` Tomas Volf [this message]
2024-07-22 14:59 ` 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=Zp1EmsX6OA9zD2N1@ws \
--to=~@wolfsden.cz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=sergio.pastorperez@outlook.es \
--cc=vincent.legoll@gmail.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).