From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 54447@debbugs.gnu.org, guix-sysadmin <guix-sysadmin@gnu.org>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#54447: cuirass: missing derivation error
Date: Mon, 16 Oct 2023 19:44:41 +0200 [thread overview]
Message-ID: <87a5si7986.fsf@gnu.org> (raw)
In-Reply-To: <87r0m2v5ih.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 10 Oct 2023 17:52:54 +0200")
Ludovic Courtès <ludo@gnu.org> skribis:
> Turns out that ‘cleanup-cuirass-roots’ in maintenance.git, used as an
> mcron job, explicitly removes GC roots for things like *-os-encrypted
> once they’re more than two days old, as well as GC roots for the
> corresponding .drv.
>
> I think this was increasing the likelihood that a .drv would be GC’d by
> the time we run the test: under high load¹, it’s plausible that a system
> test wouldn’t be built within two days after it’s been queued.
>
> I’m proposing the change below to address this; I don’t think we need
> ‘--gc-keep-outputs --gc-keep-derivations’ anymore now that we keep
> things in ‘guix publish’ cache first and foremost.
I pushed a variant of this patch:
053839d hydra: services: Leave “guix-binary.tar.xz” GC roots.
e40d961 hydra: services: Preserve Cuirass .drv GC roots.
b8fc66c hydra: cuirass: Fix build product regexps.
I didn’t dare remove “--gc-keep-derivations”. I reconfigured berlin
just now from this commit and restarted mcron (I didn’t restart
guix-daemon to avoid downtime; we should do that when the queue is close
to empty).
We’ll have to monitor disk usage to make sure it’s not negatively
affected.
Ludo’.
next prev parent reply other threads:[~2023-10-16 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 12:36 bug#54447: cuirass: missing derivation error Mathieu Othacehe
2022-08-10 9:43 ` Maxime Devos
2022-08-10 15:30 ` Maxime Devos
2022-12-10 10:57 ` Ludovic Courtès
2023-10-15 20:21 ` Ludovic Courtès
2023-10-15 20:34 ` Ludovic Courtès
2023-08-22 3:38 ` Maxim Cournoyer
2023-08-22 20:38 ` Ludovic Courtès
2023-08-30 12:17 ` 宋文武 via Bug reports for GNU Guix
2023-10-11 3:21 ` Maxim Cournoyer
2023-10-15 16:45 ` Ludovic Courtès
2023-10-16 13:25 ` Maxim Cournoyer
2023-10-16 17:39 ` Ludovic Courtès
2023-11-20 19:09 ` Maxim Cournoyer
2023-10-10 15:52 ` Ludovic Courtès
2023-10-11 3:08 ` Maxim Cournoyer
2023-10-15 20:42 ` Ludovic Courtès
2023-10-16 17:44 ` Ludovic Courtès [this message]
2024-04-04 21:33 ` Ludovic Courtès
2024-04-14 0:15 ` John Kehayias via Bug reports for GNU Guix
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=87a5si7986.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54447@debbugs.gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=othacehe@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 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).