GNU bug report logs -
#49485
[core-updates] Coreutils test failures on emulated ARMv7/AArch64
Previous Next
Reported by: Ludovic Courtès <ludo <at> gnu.org>
Date: Fri, 9 Jul 2021 09:29:02 UTC
Severity: normal
Done: Ludovic Courtès <ludo <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 49485 in the body.
You can then email your comments to 49485 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#49485
; Package
guix
.
(Fri, 09 Jul 2021 09:29:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Ludovic Courtès <ludo <at> gnu.org>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Fri, 09 Jul 2021 09:29:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
As can be seen in <https://ci.guix.gnu.org/build/657826/log/raw>, the
Coreutils test suite fails on emulated hardware because argv[0] is an
absolute file name whereas the test suite expects it to be a basename:
--8<---------------cut here---------------start------------->8---
@ build-started /gnu/store/hz81434lpq9fgsmngcad9abj72qfzqmy-coreutils-8.32.drv - aarch64-linux /var/log/guix/drvs/hz//81434lpq9fgsmngcad9abj72qfzqmy-coreutils-8.32.drv.bz2
108927
[...]
--- exp 2021-07-09 03:15:37.591279933 +0000
+++ err 2021-07-09 03:15:37.631279816 +0000
@@ -1,4 +1,4 @@
-tail: cannot fstat 'standard input'
-tail: error reading 'standard input'
-tail: no files remaining
-tail: -
+/tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/./src/tail: cannot fstat 'standard input'
+/tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/./src/tail: error reading 'standard input'
+/tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/./src/tail: no files remaining
+/tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/./src/tail: -
+ fail=1
+ tty -s
./tests/tail-2/follow-stdin.sh: line 72: /dev/tty: No such device or address
+ Exit 1
+ set +e
+ exit 1
+ exit 1
+ remove_tmp_
+ __st=1
+ cleanup_
+ kill 23630
+ 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-follow-stdin.sh.5esc
+ rm -rf /tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/gt-follow-stdin.sh.5esc
+ exit 1
FAIL tests/tail-2/follow-stdin.sh (exit status: 1)
--8<---------------cut here---------------end--------------->8---
To be continued…
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#49485
; Package
guix
.
(Fri, 09 Jul 2021 23:38:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 49485 <at> debbugs.gnu.org (full text, mbox):
Ludovic Courtès <ludo <at> gnu.org> skribis:
> As can be seen in <https://ci.guix.gnu.org/build/657826/log/raw>, the
> Coreutils test suite fails on emulated hardware because argv[0] is an
> absolute file name whereas the test suite expects it to be a basename:
[...]
> -tail: cannot fstat 'standard input'
> -tail: error reading 'standard input'
> -tail: no files remaining
> -tail: -
> +/tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/./src/tail: cannot fstat 'standard input'
> +/tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/./src/tail: error reading 'standard input'
> +/tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/./src/tail: no files remaining
> +/tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/./src/tail: -
Reading ‘binfmt-misc.rst’ in the Linux Documentation/ directory, this is
expected: by default, when using binfmt_misc, argv[0] is replaced by the
absolute file name of the executable.
The “P” flag fixes that and QEMU 6.0.0 does the right thing when that
flag is used, so commit 2ea2bca1ddb1e3ba9d843ff7544c22925de7f6d7 adds
the “P” flag by default.
Then I reconfigured the build nodes behind ci.guix with:
guix time-machine --commit=2ea2bca1ddb1e3ba9d843ff7544c22925de7f6d7 \
-- deploy berlin-nodes.scm -L modules
followed by:
for i in $(seq 159 2 185); do ssh root <at> 141.80.167.$i herd restart qemu-binfmt; done
So normally, builds at ci.guix corresponding to core-updates commit
c823b958256ba1db6cf896400fae218e4261266e and later should be done with
the “P” flag.
Ludo’.
Reply sent
to
Ludovic Courtès <ludo <at> gnu.org>
:
You have taken responsibility.
(Sat, 10 Jul 2021 13:08:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Ludovic Courtès <ludo <at> gnu.org>
:
bug acknowledged by developer.
(Sat, 10 Jul 2021 13:08:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 49485-done <at> debbugs.gnu.org (full text, mbox):
Hi!
Ludovic Courtès <ludo <at> gnu.org> skribis:
> followed by:
>
> for i in $(seq 159 2 185); do ssh root <at> 141.80.167.$i herd restart qemu-binfmt; done
>
> So normally, builds at ci.guix corresponding to core-updates commit
> c823b958256ba1db6cf896400fae218e4261266e and later should be done with
> the “P” flag.
It was not that easy… I had to reboot the machines because “P” flag
handling in QEMU requires Linux 5.12.0¹ and those machines were running
5.10 (qemu binfmt with “P” would silently fail, for some reason).
Anyway, it eventually succeeded, yay!
https://ci.guix.gnu.org/build/660330/details (aarch64-linux)
Ludo’.
¹ https://wiki.qemu.org/ChangeLog/6.0#binfmt_misc
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 08 Aug 2021 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 233 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.