From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39387@debbugs.gnu.org
Subject: bug#39387: Builds are *not* offloaded when using the "--keep-failed" or -K option.
Date: Wed, 05 Feb 2020 23:55:19 -0500 [thread overview]
Message-ID: <87sgjomi14.fsf@gmail.com> (raw)
In-Reply-To: <87y2tkzxyh.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 02 Feb 2020 18:43:50 +0100")
Hello!
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@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
next prev parent reply other threads:[~2020-02-06 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 4:57 bug#39387: Builds are *not* offloaded when using the "--keep-failed" or -K option Maxim Cournoyer
2020-02-02 17:43 ` Ludovic Courtès
2020-02-06 4:55 ` Maxim Cournoyer [this message]
2020-02-06 13:54 ` Ludovic Courtès
2020-02-06 4:56 ` Maxim Cournoyer
2020-02-06 13:55 ` Ludovic Courtès
2020-02-08 17:04 ` Maxim Cournoyer
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=87sgjomi14.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=39387@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.