Hi Ludo’, On Mon, Jun 17, 2024, at 8:11 AM, Ludovic Courtès wrote: > Hi Philip, > > "Philip McGrath" <phi...@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
