unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: guix-devel@gnu.org
Subject: Re: Semi-automated patch review
Date: Tue, 06 Apr 2021 08:43:38 +0100	[thread overview]
Message-ID: <87pmz73ljp.fsf@cbaines.net> (raw)
In-Reply-To: <7ca1c6c292d4defb23c69d019fe9af9877b521dc.camel@zaclys.net>

[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]


Léo Le Bouter <lle-bout@zaclys.net> writes:

> Cbaines already runs automated patch testing infra at
> https://data.guix-patches.cbaines.net/ and
> https://patches.guix-patches.cbaines.net/project/guix-patches/list/
>
> Considering that posting robot messages with test/lint/+ result
> information on the issues directly and on the ML might get spammy, I
> suggest that Cbaines could setup something that sends off-list to all
> the participants or just the poster of the patch being tested, as well
> as another list like guix-ci-bot@cbaines.net that reviewers could
> voluntarily subscribe to to receive all those off-list messages.
>
> Another suggestion is that the infrastructure by Cbaines could include
> an easy way to lookup CI information from a bug id and that a link to
> see such CI information could be linked to from Mumi's
> (issues.gnu.guix.org) UI. But I also really think that mailing the
> contributors privately is very important so they can get automated
> feedback and save us time without any additional setup or knowledge
> required.
>
> What do you think?

So a technical component that I have in mind for this is supporting
subscriptions to data in the Guix Data Service, and that's something
that I'm hoping to at least start implementing in the coming weeks.

Once that's a possibility for the data relevant to patch series, I think
it will be feasible to look at having more useful "checks" in Patchwork
(e.g. broken builds, new lint warnings, ...) and perhaps sending emails
to the bug to set out that information.

There's also other related work still going on, I'm hoping to merge the
Laminar package and service soon [1] which I'm currently using for this
patch testing setup, and the upcoming Outreachy project on improving the
Guix Data Service performance will greatly benefit using the Guix Data
Service for patch review.

1: https://issues.guix.gnu.org/47392

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2021-04-06  7:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 21:52 Semi-automated patch review Léo Le Bouter
2021-04-06  7:43 ` Christopher Baines [this message]
2021-04-07 15:00 ` Andreas Enge
2021-04-07 15:48   ` Vincent Legoll
2021-04-09 11:27   ` Léo Le Bouter
2021-04-09 18:07     ` Vincent Legoll

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=87pmz73ljp.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=lle-bout@zaclys.net \
    /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).