all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: CI is not processing jobs
Date: Wed, 12 Jun 2024 11:47:32 +0200	[thread overview]
Message-ID: <ZmlutEmsTuM9VoFz@jurong> (raw)
In-Reply-To: <ZmH2a_zZdBrcGWO0@jurong>

Am Thu, Jun 06, 2024 at 07:48:27PM +0200 schrieb Andreas Enge:
> Could the graph on
>    https://ci.guix.gnu.org/metrics
> be augmented by the number of packages to be built for the different
> architectures?

In that direction, the metrics now show that very few packages were built
in the last 24 hours, except maybe for ARM (where we anyway build few
packages). But the number of waiting builds stalls at around 280000.

Are these all for ARM now? Should we cancel builds a bit more aggressively
to make sure that recent packages are favoured?

Or is there a problem yet, since our ARM machines are also essentially idle?

Andreas



  reply	other threads:[~2024-06-12  9:48 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZmlutEmsTuM9VoFz@jurong \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.