From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Merging staging?
Date: Sat, 22 Dec 2018 00:06:17 +0100 [thread overview]
Message-ID: <87h8f6lbti.fsf@gnu.org> (raw)
In-Reply-To: <8736qradap.fsf@netris.org> (Mark H. Weaver's message of "Thu, 20 Dec 2018 20:17:07 -0500")
Hello Mark,
Mark H Weaver <mhw@netris.org> skribis:
> It's a good question. I have several hypotheses:
These are all valid but there’s a couple more to consider. ;-)
Specifically we’ve had ENOSPC issues on some build nodes lately, and as
I wrote elsewhere, ‘guix offload’ would report them as “permanent
failures”. Thus guix-daemon on berlin would cache those failures and
never retry afterwards. This is fixed by commit
b96e05aefd7a4f734cfec3b27c2d38320d43b687.
Commit 63b0c3eaccdf1816b419632cd7fe721934d2eb27 also arranges so we
don’t choose machines low on disk space.
Another issue I’ve noticed is “database is locked” offloading crashes,
fixed by bdf860c2e99077d431da0cc1db4fc14db2a35d31. We probably don’t
get these on hydra.gnu.org because we’re running a version that predates
the replacement of the ‘guix-register’ program by (guix store database).
There’s a few more issues about offloading in the bug tracker. I
suspect these explain the low availability of substitutes to a large
extent.
Ludo’.
next prev parent reply other threads:[~2018-12-21 23:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 14:58 Merging staging? Julien Lepiller
2018-12-20 18:36 ` Mark H Weaver
2018-12-20 22:45 ` Julien Lepiller
2018-12-21 1:17 ` Mark H Weaver
2018-12-21 9:06 ` Gábor Boskovits
2018-12-21 23:06 ` Ludovic Courtès [this message]
2018-12-23 14:00 ` Efraim Flashner
2019-01-09 16:27 ` Efraim Flashner
2019-01-09 19:15 ` Mark H Weaver
2019-01-09 19:27 ` Efraim Flashner
2019-01-10 2:27 ` Mark H Weaver
2019-01-10 22:04 ` Ludovic Courtès
2019-01-09 21:51 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2022-06-01 8:35 Release v1.4? zimoun
2022-06-03 16:41 ` Ludovic Courtès
2022-06-06 21:17 ` Merging ‘staging’? Ludovic Courtès
2022-06-08 11:50 ` Efraim Flashner
2022-06-08 21:24 ` Ludovic Courtès
2022-06-10 7:57 ` Efraim Flashner
2022-06-11 9:53 ` Ludovic Courtès
2022-06-11 10:49 ` Tom Fitzhenry
2022-06-12 3:58 ` Efraim Flashner
2022-06-12 21:08 ` Ludovic Courtès
2022-06-13 7:03 ` Ludovic Courtès
2022-06-14 4:01 ` Thiago Jung Bauermann
2022-06-09 17:19 ` pelzflorian (Florian Pelz)
2022-06-09 17:41 ` Efraim Flashner
2022-06-09 19:02 ` pelzflorian (Florian Pelz)
2022-06-10 6:07 ` pelzflorian (Florian Pelz)
2022-06-11 7:35 ` pelzflorian (Florian Pelz)
2022-06-12 4:54 ` Thiago Jung Bauermann
2022-06-12 21:06 ` Ludovic Courtès
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=87h8f6lbti.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).