From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Lars-Dominik Braun" <lars@6xq.net>
Cc: "Brian Cully" <guix-devel@gnu.org>
Subject: Re: CI is not processing jobs
Date: Sun, 16 Jun 2024 10:22:06 -0400 [thread overview]
Message-ID: <86bbccff-26c1-4a20-b8df-1faaacdd69be@app.fastmail.com> (raw)
In-Reply-To: <87ed9a3ydf.fsf@gnu.org>
Hi,
On Thu, Jun 6, 2024, at 11:05 AM, Ludovic Courtès wrote:
> Hi Guix!
>
> Ludovic Courtès <ludo@gnu.org> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> skribis:
>>
>>> The longer story is that Ricardo noticed that the build backlog had been
>>> growing for a couple of months (see “Pending builds”):
>>>
>>> https://ci.guix.gnu.org/metrics
>>>
>>> We discussed this on guix-sysadmin and found that this was due to the
>>> poor performance of a SQL query at the core of ‘cuirass remote-server’
>>> that was roughly linear in the number of packages in the database. With
>>> help from Chris Baines, this is now fixed:
>>>
>>> https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/commit/?id=17338588d4862b04e9e405c1244a2ea703b50d98
>>
>> This is now deployed on ci.guix.gnu.org.
>
> This has been running for ~4 days now; the number of pending builds has
> significantly decreased (in particular, you’ll be delighted to get
> substitutes for ‘core-updates’!):
>
> https://ci.guix.gnu.org/metrics
>
> Almost all the x86 builds have been consumed:
>
> ...
>
> The “Pending builds” plot above shows we’re reaching a plateau: this is
> because the 382,000+ remaining builds are non-x86_64 and we lack
> resources for these platforms (Arm in particular).
>
> We should probably investigate and cancel builds that correspond to old
> evaluations or now-irrelevant jobsets.
>
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?
The page at https://qa.guix.gnu.org/issue/71203 says "Issue not found: This could mean the issue does not exist, it has no patches or has been closed." The page at https://data.qa.guix.gnu.org/repository/1/branch/issue-71203 does recognize the branch, but says "No information yet". The linked commit page at https://data.qa.guix.gnu.org/revision/2805bc613df06a726035ba19e9b60762487963ef has one entry in the "Jobs" table, "created 2024-05-26 06:07:51.458233".
I have only surface-level familiarity with the QA system, so sorry if I'm missing something!
Thanks,
Philip
next prev parent reply other threads:[~2024-06-16 14:23 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 [this message]
2024-06-17 12:11 ` qa.guix delays in processing patches Ludovic Courtès
2024-06-19 4:45 ` Philip McGrath
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=86bbccff-26c1-4a20-b8df-1faaacdd69be@app.fastmail.com \
--to=philip@philipmcgrath.com \
--cc=guix-devel@gnu.org \
--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).