From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: libc-alpha@sourceware.org
Subject: failures on Raspberry Pi
Date: Sun, 31 Jan 2021 08:33:09 +0100 [thread overview]
Message-ID: <mwo8h54l3e.fsf@tomate.loria.fr> (raw)
Hi,
I get 8 test failures on a Raspberry Pi (ARMv7 Processor rev 5 (v7l)) with
commit 934c48a and gcc 10.2.1:
Summary of test results:
8 FAIL
3930 PASS
18 UNSUPPORTED
17 XFAIL
2 XPASS
FAIL: elf/tst-glibc-hwcaps-prepend-cache
tst-glibc-hwcaps-prepend-cache.c:109: numeric comparison failure
left: 2 (0x2); from: marker1 ()
right: 3 (0x3); from: 3
error: tst-glibc-hwcaps-prepend-cache.c:118: not true: dlopen (SONAME, RTLD_NOW) == NULL
error: 2 test failures
running post-clean rsync
FAIL: locale/tst-localedef-path-norm
info: Directory '/usr/lib/locale/en_US1.utf8' exists.
Timed out: killed the child process
Termination time: 2021-01-29T12:51:15.067421847
Last write to standard output: 2021-01-29T12:51:10.320779487
running post-clean rsync
FAIL: localedata/sort-test
cmn_TW.UTF-8 xfrm-test FAIL
FAIL: misc/tst-sysvshm-linux
../sysdeps/unix/sysv/linux/tst-sysvshm-linux.c:155: numeric comparison failure
left: 4278190079 (0xfeffffff); from: ipcinfo.shmmax
right: 2147483647 (0x7fffffff); from: tipcinfo.shmmax
error: 1 test failures
FAIL: nss/tst-nss-files-hosts-getent
Timed out: killed the child process
Termination time: 2021-01-29T16:20:09.398286002
Last write to standard output: 2021-01-29T16:19:49.383886436
FAIL: nss/tst-nss-files-hosts-multi
Timed out: killed the child process
Termination time: 2021-01-29T16:19:47.876326179
Last write to standard output: 2021-01-29T16:19:07.863774643
FAIL: stdio-common/tst-vfprintf-width-prec
Timed out: killed the child process
Termination time: 2021-01-29T14:17:07.870905125
Last write to standard output: 2021-01-29T14:16:47.850422358
FAIL: stdio-common/tst-vfprintf-width-prec-mem
Memory not freed:
-----------------
Address Size Caller
0x70a5f008 0x31fff9c at 0x76e814cf
I can provide more details if needed. For the tests with "timed out", is there
a way to increase the default timeout threshold?
Paul
next reply other threads:[~2021-01-31 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 7:33 Paul Zimmermann [this message]
2021-01-31 11:17 ` Florian Weimer
2021-02-01 21:09 ` Paul Zimmermann
2021-02-02 12:17 ` Adhemerval Zanella
2021-02-03 5:16 ` Paul Zimmermann
2021-02-03 6:14 ` Paul Zimmermann
2021-02-02 18:19 ` Joseph Myers
2021-02-02 18:32 ` Carlos O'Donell
2021-02-02 19:30 ` Florian Weimer
2021-02-02 20:32 ` H.J. Lu
2021-02-03 4:50 ` Paul Zimmermann
2021-02-03 5:22 ` Paul Zimmermann
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=mwo8h54l3e.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=libc-alpha@sourceware.org \
/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.
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).