unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: Adam Faiz <adam.faiz@disroot.org>
Cc: tumashu@163.com, guix-devel@gnu.org
Subject: Re: How to always keep build tree when run guix build.
Date: Wed, 17 Jan 2024 11:08:10 +0100	[thread overview]
Message-ID: <ZaenCtjXIXbkdFqp@ws> (raw)
In-Reply-To: <77956f5f-d901-41f0-185e-b79b462c182d@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On 2024-01-17 16:21:05 +0800, Adam Faiz wrote:
> Hello,
> 
> > Hello:
> > 
> >   How to always keep build tree when run guix build, at the moment, I 
> > use --keep-failed, but it will remove build tree when build success, the
> > problem is that build success alway not right build success :-), I need
> > go to build tree to check some thing.
> > 
> > Thanks!
> > 
> > 
> > -- 
> 
> You can add the `--cache-failures` option when starting the guix-daemon, which tells it to keep the build failures by default.
> It's explained in more detail in the "Invoking guix-daemon" section of the Guix manual:
> https://guix.gnu.org/en/manual/devel/en/html_node/Invoking-guix_002ddaemon.html
>

I think the question was how to keep all build trees, including the build trees
from successful builds.

Have a nice day,
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 --]

      parent reply	other threads:[~2024-01-17 10:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16  6:21 How to always keep build tree when run guix build Feng Shu
2024-01-17  8:21 ` Adam Faiz
2024-01-17  8:34   ` Efraim Flashner
2024-01-17  8:42   ` Feng Shu
2024-01-17 10:08   ` Tomas Volf [this message]

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=ZaenCtjXIXbkdFqp@ws \
    --to=~@wolfsden.cz \
    --cc=adam.faiz@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=tumashu@163.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).