GNU bug report logs - #39387
Builds are *not* offloaded when using the "--keep-failed" or -K option.

Previous Next

Full log

Message #15 received at 39387 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 39387 <at> debbugs.gnu.org
Subject: Re: bug#39387: Builds are *not* offloaded when using the
 "--keep-failed" or -K option.
Date: Wed, 05 Feb 2020 23:55:19 -0500

Hello!

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

> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
>
>> In the second case, the build is started on the local machine instead of
>> being dispatched to the offload machine.  Presumably, this is done so
>> that the files are available locally; but I'd prefer if it'd offload and
>> keep the files on the remote.  An alternative would be to copy the remote build directory
>> locally after failure.
>
> Indeed, it’s a feature!  :-)  It was discussed here:
>
>   https://issues.guix.gnu.org/issue/38312
>
> There we discussed the possibility of printing a warning, which wasn’t
> implemented.

I see!

> I’m closing in the meantime, but let me know what you think!

OK!  I think I now see the technical difficulties in implementing a
useful, offloaded interrupted build: the build artifacts, even if copied
locally, would require syncing all the build time dependencies in order
to allow sourcing the "environment-variables" script and be able to
debug.  That's more the job of 'guix publish', not of 'guix offload'.

Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.