From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 33124-done@debbugs.gnu.org
Subject: bug#33124: Cuirass: register GC roots for evaluations under /var/guix/gcroots
Date: Wed, 07 Nov 2018 15:29:38 +0100 [thread overview]
Message-ID: <87o9b1ufjh.fsf@gnu.org> (raw)
In-Reply-To: <877ei9ypvh.fsf@lassieur.org> ("Clément Lassieur"'s message of "Tue, 23 Oct 2018 11:27:30 +0200")
Hi Clément,
Clément Lassieur <clement@lassieur.org> skribis:
> I think the goal here is to make sure that the builds that resulted from
> of 1) important evaluations (releases) and 2) recent evaluations aren't
> garbage collected.
>
> <sneek> snape, civodul says: i think Cuirass should register GC roots for its
> evaluations under /var/guix/gcroots
> <snape> [...] How many such evaluations should be registered? If all
> are registered, we'll run out of space won't we? So would it be
> like the last 15 or something?
> <civodul> snape: i think we'd register all of them and use (guix cache) to
> automatically wipe old ones periodically [09:53]
> <civodul> snape: when there's a release we could manually stash important
> evaluations away so they won't be deleted
> <civodul> so i'd just create one subdir for each eval say in
> /var/guix/profiles/USER/cuirass/evaluations [09:54]
> <civodul> and that'd contain a bunch of symlinks to both the .drv and the
> outputs
I went ahead and implemented a simple version of this in commit
d4623d50edac4a6e81f5986a91c2818f5fc4965d.
Let me know what you think!
Ludo’.
next prev parent reply other threads:[~2018-11-07 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 9:27 bug#33124: Cuirass: register GC roots for evaluations under /var/guix/gcroots Clément Lassieur
2018-11-07 14:29 ` Ludovic Courtès [this message]
2018-11-07 19:24 ` Clément Lassieur
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=87o9b1ufjh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33124-done@debbugs.gnu.org \
--cc=clement@lassieur.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 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).