unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Lars-Dominik Braun" <lars@6xq.net>,
	guix-devel@gnu.org, "Christopher Baines" <guix@cbaines.net>
Subject: Re: qa.guix delays in processing patches
Date: Wed, 19 Jun 2024 00:45:29 -0400	[thread overview]
Message-ID: <1fcfbc84-2ac7-4be0-bdc5-8fbcfa91cefa@app.fastmail.com> (raw)
In-Reply-To: <87ed8vahwn.fsf_-_@gnu.org>

Hi Ludo’,

On Mon, Jun 17, 2024, at 8:11 AM, Ludovic Courtès wrote:
> Hi Philip,
>
> "Philip McGrath" <philip@philipmcgrath.com> skribis:
>
>> For some reason QA still doesn't seem to be working for https://issues.guix.gnu.org/71203 (a Racket update I sent on May 26), which I suspect may be related to this. Could someone take a look?
>>
>> [...]
>>
>> I have only surface-level familiarity with the QA system, so sorry if I'm missing something!
>
> As you may know, qa.guix is using separate hardware and software
> infrastructure from ci.guix, based on the Build Coordinator and the Data
> Service.
>

Oh, I totally missed that distinction! I know both Cuirass and the Build Coordinator/Data Service exist, but I hadn't thought about which provided each service, and I guess I was unconsciously thinking of "CI" and "QA" as synonyms.

>
> Anyway, there’s a trick: Philip, if you rebase your patch series and
> resend it, qa.guix is like to consider it again and to spawn builds.
> Please consider doing that!
>

Thanks! I did that about 36 hours ago, and https://qa.guix.gnu.org/issue/71203 indeed recognized it, though it still is in the "yet to process revision" state.

> It’s unclear to me why issues are sometimes seemingly not picked up.
> Chris, do you have more insight into this?

I should have mentioned this in my last email, but, when I first sent the patch series, it *had* been picked up as https://qa.guix.gnu.org/issue/71203 and gotten to the "yet to process revision" state. I checked in on it a few times, and it remained in that state: only the last time (before rebasing) did it say "issue not found", though I'm not sure how long it had been since I'd last checked. I guess one thing I'm realizing is I don't know how long is normal for QA to take vs. when I should report a potential problem.

Thanks,
Philip


  reply	other threads:[~2024-06-19  4:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31  6:25 CI is not processing jobs Lars-Dominik Braun
2024-06-01 14:09 ` Ludovic Courtès
2024-06-02 21:14   ` Ludovic Courtès
2024-06-06 15:05     ` Ludovic Courtès
2024-06-06 17:48       ` Andreas Enge
2024-06-12  9:47         ` Andreas Enge
2024-06-12 14:50           ` Maxim Cournoyer
2024-06-17 12:07           ` Little progress on powerpc64le and aarch64 builds on ci.guix Ludovic Courtès
2024-06-07  6:38       ` CI is not processing jobs Lars-Dominik Braun
2024-06-16 14:22       ` Philip McGrath
2024-06-17 12:11         ` qa.guix delays in processing patches Ludovic Courtès
2024-06-19  4:45           ` Philip McGrath [this message]
2024-06-19 13:50           ` Christopher Baines
2024-06-25 20:07             ` Philip McGrath
2024-06-27 13:32               ` Andreas Enge
2024-07-09 10:36               ` Christopher Baines

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=1fcfbc84-2ac7-4be0-bdc5-8fbcfa91cefa@app.fastmail.com \
    --to=philip@philipmcgrath.com \
    --cc=guix-devel@gnu.org \
    --cc=guix@cbaines.net \
    --cc=lars@6xq.net \
    --cc=ludo@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).