From: "Ludovic Courtès" <ludo@gnu.org>
To: <guix-devel@gnu.org>
Subject: Cuirass upgrade on ci.guix
Date: Mon, 02 Oct 2023 23:46:49 +0200 [thread overview]
Message-ID: <87leckg0ja.fsf@gnu.org> (raw)
Hello Guix!
A few hours ago I deployed current Cuirass on ci.guix and its build
machines. The expected benefits are:
1. Better throughput. I fixed a bug that would lead “workers” to
eventually get ignored by ‘cuirass remote-server’, meaning they
would become idle until either the server or the worker is
restarted¹.
When I reconfigured, there were 45k pending builds (!), visible on
<https://ci.guix.gnu.org/metrics> and the vast majority of workers
at <https://ci.guix.gnu.org/workers> were idle.
We’re now at ~22k pending builds (okay, I cheated by canceling ~15k
from ‘emacs-team’, but I also restarted many builds en masse),
which are mostly non-x86.
My hope is that we can get close to zero soon and have headroom for
feature branches.
2. Evaluation can be triggered via POST requests, which should make
things a bit more reactive and will allow us to poll repos less
frequently. I submitted a support request on Savannah:
<https://savannah.nongnu.org/support/?110939>.
3. Improved resilience against “evaluation storms” since ‘cuirass
register’ now has an upper limit on the number of evaluations that
may occur in parallel.
4. Build priority handling has been restored (it had been lost
recently).
As a bonus, we may finally get native GNU/Hurd builds again, via the
childhurds running on some of the build nodes.
That’s it!
Ludo’.
¹ https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/commit/?id=40f70d28aed55c404cca6a0760860fb4942e6bee
next reply other threads:[~2023-10-02 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 21:46 Ludovic Courtès [this message]
2023-10-04 5:37 ` Cuirass upgrade on ci.guix Janneke Nieuwenhuizen
2023-10-04 8:47 ` Mathieu Othacehe
2023-10-04 9:53 ` Simon Tournier
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=87leckg0ja.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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).