From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: QA and armhf
Date: Fri, 13 Sep 2024 12:37:49 +0200 [thread overview]
Message-ID: <ZuQV_dEnmu_Mo7hB@jurong> (raw)
Hello,
after the core-updates merge, QA is not keeping up; on
https://qa.guix.gnu.org/patches
I see the message
Builds for new patch series suspended as master branch substitute availability is low for: armhf-linux
Maybe buying new ARM machines could be part of the solution, but I also
think that armhf (and i686) should not hold up progress of Guix, or, as it
stands, risk the Guix quality since people end up pushing regardless of
the QA status (if I remember well, the manual suggests a one-week waiting
period, which right now causes frustrating busy work - create an issue,
send the patch series if there are several commits, wait a week while
knowing that QA will not handle the patch, push, close the issue).
Notice that ci has already completely dropped armhf substitutes:
https://qa.guix.gnu.org/branch/master
Could we drop this suspension of QA depending on armhf and i686 weather
status on the master branch, and only keep it for aarch64 and x86_64?
Andreas
next reply other threads:[~2024-09-13 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 10:37 Andreas Enge [this message]
2024-09-13 10:50 ` QA and armhf Andreas Enge
2024-09-30 0:17 ` John Kehayias
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=ZuQV_dEnmu_Mo7hB@jurong \
--to=andreas@enge.fr \
--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).