unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: Update on automating testing of patches and qa.guix.gnu.org
Date: Mon, 07 Nov 2022 09:51:39 +0100	[thread overview]
Message-ID: <87eduf9mg4.fsf@gmail.com> (raw)
In-Reply-To: <87r0yhhaff.fsf@cbaines.net>

Hi Chris,

Thanks!  Really cool.

On sam., 05 nov. 2022 at 12:24, Christopher Baines <mail@cbaines.net> wrote:

>  - The creation of the patch branches is now handled here (rather than
>    through scripts run by Laminar)

Is it possible to have access to the branch?  As discussed with Josselin
at 10 Years Days, we could have in mind the workflow:

    guix time-machine --url=https://qa.guix.gnu.org \
                      --branch=58812                \
         -- shell --symlink

for quickly testing a specific patch without going to manually clone,
apply the patch, then run ./bootstrap, ./configure and last use
./pre-inst-env.


> 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.

Do you expose the list of these green patches?  It could be cool to have
a command line – an option of “guix weather” or a specific CLI – to
collect information of the status.  WDYT?

>                                                 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).

Mark it as ’moreinfo’ via Debbugs?  Or something else?


Cheers,
simon



  reply	other threads:[~2022-11-07  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 11:24 Update on automating testing of patches and qa.guix.gnu.org Christopher Baines
2022-11-07  8:51 ` zimoun [this message]
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

  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=87eduf9mg4.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.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).