From: Leo Famulari <leo@famulari.name>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: hikari build failure
Date: Wed, 31 Mar 2021 01:15:52 -0400 [thread overview]
Message-ID: <YGQFiN34upu5soUN@jasmine.lan> (raw)
In-Reply-To: <CAEwRq=qdSKBxC-Cktj+QBiP+3unvu3fb177NP=Gs1oMTcNgY7A@mail.gmail.com>
On Tue, Mar 30, 2021 at 11:58:57PM +0200, Vincent Legoll wrote:
> > I've restarted <https://ci.guix.gnu.org/build/133895/details>.
>
> I'm seeing overdrive1 as idle (as a lot of hydra workers) yet the
> restart is still in scheduled state.
>
> What am I missing ?
I don't know exactly what happened here.
In general, most of the aarch64 substitutes are currently built using
(very slow) QEMU emulation on x86_64 machines.
Half of the x86_64 machines are reserved for this, and it seems like
they can never finish their tasks, compared to the machines building for
x86_64 / i686. This creates the distinctive "checkerboard" pattern often
seen at <https://ci.guix.gnu.org/workers>.
So, maybe your job was being handled by one of the x86_64-based
machines.
Anyways, I retried the bmake derivation on an Overdrive, and it
succeeded there.
The failure log doesn't say why it failed, but it does say 'command
"make" "-j" "16" "INSTALL=install" failed with status 2'. Who knows,
maybe it's not designed to run with so many threads. Our overdrives only
have 4. Or maybe the emulation is just not good enough.
The hikari derivation also built successfully on an Overdrive. It should
be possible to retrieve substitutes now.
prev parent reply other threads:[~2021-03-31 5:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 21:20 hikari build failure Vincent Legoll
2021-03-30 21:26 ` Tobias Geerinckx-Rice
2021-03-30 21:58 ` Vincent Legoll
2021-03-31 5:15 ` Leo Famulari [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=YGQFiN34upu5soUN@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=vincent.legoll@gmail.com \
/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).