From: Efraim Flashner <efraim@flashner.co.il>
To: ng0 <ng0@n0.is>
Cc: 24168@debbugs.gnu.org
Subject: bug#24168: Offloading builds does not honor --keep-failed
Date: Fri, 25 Oct 2019 13:47:49 +0300 [thread overview]
Message-ID: <20191025104749.GL15460@E5400> (raw)
In-Reply-To: <877fb5akoe.fsf@we.make.ritual.n0.is>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
On Wed, Aug 24, 2016 at 10:04:01PM +0000, ng0 wrote:
> ng0 <ng0@we.make.ritual.n0.is> writes:
>
> > ng0 <ng0@we.make.ritual.n0.is> writes:
> >
Offloading still does not honor --keep-failed, but with
b3673e9917217fc27c743092e58e4eb33d0fdd16 there is at least a warning
about it now.
> >> This bug is to keep track of and not forget to add this feature to
> >> build offloading:
> >>
> >> When I offload builds to my build machine(s), I want to keep the results
> >> of failed builds to investigate the reason for failure.
> >>
> >> Currently this does not happen with offloading, we should fix this as
> >> its a nice feature to have.
> >
> > Adding to this: offloading does not support `guix build --keep-going`
> > either.
> >
>
> Additionally with enabled offloading, guix pull has no option to build
> on its own when the build machines are down.
>
> Being able to pass something like
> guix pull -- --no-build-hook
> would be good.
>
Not sure when it was added, but 'guix pull --no-build-hook' does work
(now).
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-25 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 12:48 bug#24168: Offloading builds does not honor --keep-failed ng0
2016-08-14 18:28 ` ng0
2016-08-24 22:04 ` ng0
2019-10-25 10:47 ` Efraim Flashner [this message]
2019-10-25 21:10 ` Ludovic Courtès
2019-10-28 22:45 ` Marius Bakke
2020-04-07 19:29 ` Marius Bakke
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=20191025104749.GL15460@E5400 \
--to=efraim@flashner.co.il \
--cc=24168@debbugs.gnu.org \
--cc=ng0@n0.is \
/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.