From: Ricardo Wurmus <rekado@elephly.net>
To: pukkamustard <pukkamustard@posteo.net>
Cc: 53903@debbugs.gnu.org
Subject: bug#53903: aarch64: failed to compute the derivation for Guix
Date: Fri, 11 Feb 2022 14:05:28 +0100 [thread overview]
Message-ID: <875yplv9eo.fsf@elephly.net> (raw)
In-Reply-To: <86k0e1v9l7.fsf@posteo.net>
pukkamustard <pukkamustard@posteo.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> [..]
>>
>>>
>>> I tried building it again on the Overdrive machine, and it succeeded. I
>>> also tried building it with --cores=1 on the HoneyComb machine and that
>>> succeeded too.
>>
>> I have not been able to build this on Kreuzberg (a HoneyComb machine)
>> with “--cores=1”. The same test keeps failing. I tried this at least
>> five times.
>
> I'm seeing the same issue on a PinePhone (running PostmarketOS).
>
> Using "--cores=1" does not solve the issue for me. The same test keeps
> failing.
Thanks for reproducing this!
As a workaround I copied the successful build from an Overdrive machine
to ci.guix.gnu.org and substituted it on the HoneyComb machine.
Unfortunately, there’s yet another build that fails in the same manner
(/gnu/store/zakwql6wdm7rvq0grdfl3qa6b60s9px1-coreutils-minimal-8.32.drv); I’ll have the Overdrive build
it, so that the HoneyCombs can continue.
Clearly something’s up there and needs fixing. But I can’t justify
keeping the three HoneyComb nodes idle, so I’m substituting these
builds.
--
Ricardo
next prev parent reply other threads:[~2022-02-11 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 18:48 bug#53903: aarch64: failed to compute the derivation for Guix Ricardo Wurmus
2022-02-09 20:25 ` Christopher Baines
2022-02-10 0:14 ` Ricardo Wurmus
2022-02-10 9:30 ` Christopher Baines
2022-02-10 9:49 ` Ricardo Wurmus
2022-02-10 11:20 ` Christopher Baines
2022-02-10 15:35 ` Ricardo Wurmus
2022-02-11 12:55 ` pukkamustard
2022-02-11 13:05 ` Ricardo Wurmus [this message]
2022-02-09 23:56 ` Ricardo Wurmus
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=875yplv9eo.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=53903@debbugs.gnu.org \
--cc=pukkamustard@posteo.net \
/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.