From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Getting back to testing patches on qa.guix.gnu.org
Date: Wed, 10 May 2023 13:33:24 +0100 [thread overview]
Message-ID: <87fs841gll.fsf@cbaines.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
Hey!
Two weeks ago I disabled the qa-frontpage submitting builds for patches
[1] since there wasn't much point continuing to submit the builds while
the bordeaux build farm caught up with the merge.
1: https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=6343780896fcdfdeccfbaf9ef407ceb4641f33b7
Unfortunately, I'm still waiting for it to catch up, you can see the
substitute availability numbers for yourself here [2].
2: https://qa.guix.gnu.org/branch/master
After the core-updates merge, there's also been a mesa update and the
merge of rust-team, both of which involve quite a lot of builds. Plus
things have been a bit bumpy for the bordeaux build farm which doesn't
help. The coordinator has been frequently crashing [3] and the
derivations for i586-gnu have been changing every revision, which slows
down submitting the rest of the builds.
3: https://issues.guix.gnu.org/63368
While I'm continuing to play whac-a-mole with the broken derivation
issues, I think I've managed to resolve the crashing issue with the
build coordinator, so I think the main thing needed is time without any
large rebuilds.
More hardware would of course be helpful, but that's more of a medium
term issue.
Even though there's been discussion about process changes, nothing has
changed yet [4] and commits affecting 300 or more packages according to
guix refresh should still go to staging/core-updates, so there shouldn't
be lots of rebuilds in the coming days anyway.
4: https://guix.gnu.org/manual/devel/en/html_node/Submitting-Patches.html
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
reply other threads:[~2023-05-10 13:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs841gll.fsf@cbaines.net \
--to=mail@cbaines.net \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.