hikari build failure

hikari build failure

[Vincent Legoll]

Hello,

I saw the aarch64 build failure for hikari on cuirass
https://ci.guix.gnu.org/build/133895/details
it looked like the failure was because bmake (a dep)
failed, I tried to build it locally which succeded, then
also retried hikari with success.

I'm on a binary install above armbian on odroid N2.

vince@odroidn2:~$ guix describe
Génération 2    30 mars 2021 22:59:41    (actuelle)
  guix 634d984
    URL du dépôt : https://git.savannah.gnu.org/git/guix.git
    branche : master
    commit : 634d9845a6b4e362f32ba369ae42851719455ba3

The retry button on cuirass gave me a 403 forbidden.

What should we do ? just wait for next build ?

-- 
Vincent Legoll

Re: hikari build failure

[Tobias Geerinckx-Rice]

Vincent Legoll writes:
> What should we do ? just wait for next build ?

I've restarted <https://ci.guix.gnu.org/build/133895/details>.

Kind regards,

T G-R

Re: hikari build failure

[Vincent Legoll]

> 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 ?

-- 
Vincent Legoll

Re: hikari build failure

[Leo Famulari]

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.