emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#49485: closed ([core-updates] Coreutils test failures on emulated AR


From: GNU bug Tracking System
Subject: bug#49485: closed ([core-updates] Coreutils test failures on emulated ARMv7/AArch64)
Date: Sat, 10 Jul 2021 13:08:02 +0000

Your message dated Sat, 10 Jul 2021 15:07:30 +0200
with message-id <87lf6ee2r1.fsf@gnu.org>
and subject line Re: bug#49485: [core-updates] Coreutils test failures on 
emulated ARMv7/AArch64
has caused the debbugs.gnu.org bug report #49485,
regarding [core-updates] Coreutils test failures on emulated ARMv7/AArch64
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
49485: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=49485
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [core-updates] Coreutils test failures on emulated ARMv7/AArch64 Date: Fri, 09 Jul 2021 11:28:10 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
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’.



--- End Message ---
--- Begin Message --- Subject: Re: bug#49485: [core-updates] Coreutils test failures on emulated ARMv7/AArch64 Date: Sat, 10 Jul 2021 15:07:30 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Hi!

Ludovic Courtès <ludo@gnu.org> skribis:

> followed by:
>
>   for i in $(seq 159 2 185); do ssh root@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


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]