From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Update on automating testing of patches and qa.guix.gnu.org
Date: Sat, 05 Nov 2022 12:24:36 +0100 [thread overview]
Message-ID: <87r0yhhaff.fsf@cbaines.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
Hey!
I last emailed guix-devel on this topic back in September:
https://lists.gnu.org/archive/html/guix-devel/2022-09/msg00054.html
https://lists.gnu.org/archive/html/guix-devel/2022-09/msg00159.html
Along with some general improvements and fixes, the following things
might be interesting:
- There are now some bigger badges for the overall status of patch
issues, thanks Arun!
- The sort order for the patches page should now be more useful
- The creation of the patch branches is now handled here (rather than
through scripts run by Laminar)
- There is a mailto link on the issue page to toggle the moreinfo
status, thanks Efraim for the idea!
- The issue page has a "review checklist". I based this off of
something Arun suggested for Mumi. The form doesn't do anything, I'm
just using it as a reminder of things to check when reviewing
patches.
In terms of next steps:
- I'm still looking to move this repository on to Savannah, my initial
attempt failed, so I'm not sure how to do this.
- Currently it's hard to distinguish "Unknown" builds in to builds
where some dependency has failed, and builds which just haven't
happened yet. I'm going to try and change the Guix Data Service to
provide information on blocking builds in the comparison.
- For more things, see the README
https://git.cbaines.net/guix/qa-frontpage/about/
I'm finding this really useful to highlight simple patches which have
had some testing done automatically. I'd encourage others who are
interested in merging patches to try looking at the patches showing up
as green, as hopefully they're in a good state. If there's any which
aren't (e.g. needs some changes or more discussion), you can mark it as
moreinfo to push it down the list (there's a link on the right to do
this).
Do let me know if you have any comments or questions! This should be
easy to hack on as well, and I'm happy to try and help.
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next reply other threads:[~2022-11-05 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 11:24 Christopher Baines [this message]
2022-11-07 8:51 ` Update on automating testing of patches and qa.guix.gnu.org zimoun
2022-11-07 9:36 ` Christopher Baines
2022-11-09 10:39 ` zimoun
2022-11-10 11:55 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0yhhaff.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.