unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 39387@debbugs.gnu.org
Subject: bug#39387: Builds are *not* offloaded when using the "--keep-failed" or -K option.
Date: Thu, 06 Feb 2020 14:54:38 +0100	[thread overview]
Message-ID: <87k14z95y9.fsf@gnu.org> (raw)
In-Reply-To: <87sgjomi14.fsf@gmail.com> (Maxim Cournoyer's message of "Wed, 05 Feb 2020 23:55:19 -0500")

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

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

[...]

>> 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'.

Right.  Ideally the build directory of an offloaded could be copied back
to the host of the caller, but that’s not implemented and a bit tricky
maybe.

Before this change, my main use of ‘--no-build-hook’ would be together
with ‘-K’ for that reason.

Ludo’.

  reply	other threads:[~2020-02-06 13:55 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
2020-02-06 13:54     ` Ludovic Courtès [this message]
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

  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=87k14z95y9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39387@debbugs.gnu.org \
    --cc=maxim.cournoyer@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).