From: Ricardo Wurmus <rekado@elephly.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 53903@debbugs.gnu.org
Subject: bug#53903: aarch64: failed to compute the derivation for Guix
Date: Thu, 10 Feb 2022 16:35:15 +0100 [thread overview]
Message-ID: <87tud6vimm.fsf@elephly.net> (raw)
In-Reply-To: <874k57dkzx.fsf@cbaines.net>
Christopher Baines <mail@cbaines.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>>>>> View build log at '/var/log/guix/drvs/2j/5348zpz32qmb7x4v5ipg26d269hgxf-coreutils-8.32.drv.bz2'.
>>>>>
>>>>> Would you be able to share this log, or at least the last bit of it?
>>>>
>>>> There’s one failing test:
>>>>
>>>> ==> foo <==
>>>> + fail=1
>>>> + break
>>>> + Exit 1
>>>> + set +e
>>>> + exit 1
>>>> + exit 1
>>>> + remove_tmp_
>>>> + __st=1
>>>> + cleanup_
>>>> + kill 23895
>>>> + wait 23895
>>>> + test '' = yes
>>>> + cd /tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32
>>>> + chmod -R u+rwx /tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/gt-assert.sh.B8Wf
>>>> + rm -rf /tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/gt-assert.sh.B8Wf
>>>> + exit 1
>>>> FAIL tests/tail-2/assert.sh (exit status: 1)
>>>
>>> I tried building this derivation on the HoneyComb machine hooked up to
>>> bordeaux.guix.gnu.org, and it fails to build in the same way.
>>>
>>> Maybe this is a failure that happens (or is more likely) with more
>>> cores. The linux-libre version is slightly different on monokuma as
>>> well, it's running 5.12.17-gnu currently.
>>
>> Thanks for reproducing this issue! I wonder what we should do about
>> this; is it a real problem in coreutils, a problem with the test suite,
>> or something else.
>>
>> To get past this we could replace coreutils on aarch64 with a package
>> that disables this test, but before attempting to implement this
>> workaround I’d like to know if there’s a real problem that also needs to
>> be addressed.
>
> 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.
--
Ricardo
next prev parent reply other threads:[~2022-02-10 17:46 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 [this message]
2022-02-11 12:55 ` pukkamustard
2022-02-11 13:05 ` Ricardo Wurmus
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=87tud6vimm.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=53903@debbugs.gnu.org \
--cc=mail@cbaines.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.