From: Thiago Jung Bauermann via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 49752@debbugs.gnu.org
Subject: bug#49752: [coreu-updates] coreutils-final test failures on powerpc64le-linux
Date: Tue, 27 Jul 2021 20:34:55 -0300 [thread overview]
Message-ID: <10489841.2qH5l5Hjcy@popigai> (raw)
Hi,
On core-updates, as of the following commit from July 26th:
e2690a8eb2df gnu: mes-rb5: Remove.
Guix fails to build ‘(@@ (gnu packages commencement) coreutils-final)’ on
powerpc64le-linux. E.g.: https://ci.guix.gnu.org/build/692547/details
The problem happens during the ‘check’ phase, because of two testsuite
failures:
================================================
GNU coreutils 8.32: ./tests/test-suite.log
================================================
# TOTAL: 620
# PASS: 408
# SKIP: 210
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0
The failures are:
FAIL: tests/misc/env-signal-handler
FAIL: tests/misc/timeout
In both of them, the problem is the same: the test expects the ‘timeout’
utility to print the name of the signal that is being sent, but for some
reason it only prints the first letter of the name. E.g.:
+ diff -u exp-err6 err6
--- exp-err6 2021-07-26 19:00:08.159279146 +0000
+++ err6 2021-07-26 19:00:08.475277881 +0000
@@ -1,2 +1,2 @@
-timeout: sending signal INT to command 'env'
-timeout: sending signal KILL to command 'env'
+timeout: sending signal I to command 'env'
+timeout: sending signal K to command 'env'
It’s interesting that this works as expected with the ‘coreutils-boot0’
package.
--
Thanks,
Thiago
next reply other threads:[~2021-07-27 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 23:34 Thiago Jung Bauermann via Bug reports for GNU Guix [this message]
2021-08-04 23:36 ` bug#49752: [coreu-updates] coreutils-final test failures on powerpc64le-linux Thiago Jung Bauermann via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10489841.2qH5l5Hjcy@popigai \
--to=bug-guix@gnu.org \
--cc=49752@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).