From: "Brennan Vincent" <brennan@umanwizard.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: CI idle for aarch64?
Date: Thu, 24 Oct 2024 21:49:40 -0400 [thread overview]
Message-ID: <87ldyd7xzf.fsf@denver.mail-host-address-is-not-set> (raw)
In-Reply-To: <87from4mp3.fsf@gnu.org>
Thanks Ludo. Makes perfect sense.
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> "Brennan Vincent" <brennan@umanwizard.com> skribis:
>
>> While trying to understand why I can't build Skia on aarch64 (see
>> https://issues.guix.gnu.org/issue/73659) , I tried looking at the logs
>> in CI. The Skia build is listed as "Scheduled":
>> http://ci.guix.gnu.org/build/5915482/details . But nothing is being
>> built on any of the aarch64 currently. So why has the build not started?
>
> Unfortunately, build machines can be reported as idle even though
> they’re building things.
>
> The reason for this is a design issue in Cuirass, which knows about
> “builds” assigned to build machines, but not about derivations actually
> being built (“builds” here are the things you explicitly asked Cuirass
> to build; on <https://ci.guix.gnu.org/jobset/master>, that includes
> most packages, but not all.)
>
> Often, before they can perform the “build” they were given, build
> machines must build other derivations that the given build depends on.
> Those are currently not shown at <https://ci.guix.gnu.org/workers>.
> It’s really a bug that should be fixed.
>
> There can also be other reasons why a build machine appears to be idle:
> because it’s (re)trying to substitute a derivation it was asked to
> build, because it’s running out of disk space, etc. Those should be
> less frequent though.
>
> Ludo’.
prev parent reply other threads:[~2024-10-25 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 14:47 CI idle for aarch64? Brennan Vincent
2024-10-23 19:57 ` Ludovic Courtès
2024-10-25 1:49 ` Brennan Vincent [this message]
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=87ldyd7xzf.fsf@denver.mail-host-address-is-not-set \
--to=brennan@umanwizard.com \
--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 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).