From: Xi Ruoyao <xry111@xry111.site>
To: libc-alpha@sourceware.org
Cc: caiyinyu <caiyinyu@loongson.cn>, Wang Xuerui <i@xen0n.name>
Subject: Strange test failures on LoongArch
Date: Sat, 25 Mar 2023 22:15:13 +0800 [thread overview]
Message-ID: <3022ff730b2677f8bce36e48dd5aeb6c7bd6b93d.camel@xry111.site> (raw)
Hi,
When I test my "avoid va_list" patches, I found 3 test failures on
LoongArch:
$ cat elf/tst-ldconfig-soname.out
/home/xry111/git-repos/glibc-build/elf/bug30125-test-directory/lib: (from <cmdline>:0)
error: tst-ldconfig-soname.sh - extra symlinks found
$ cat elf/tst-ldconfig-ld_so_conf-update.out
error: tst-ldconfig-ld_so_conf-update.c:112: not true: dlopen (DSO, RTLD_NOW | RTLD_GLOBAL) != NULL
error: 1 test failures
running post-clean rsync
$ cat elf/tst-glibc-hwcaps-prepend-cache.out
error: xdlfcn.c:29: error: dlopen: libmarkermod1.so: cannot open shared object file: No such file or directory
error: 1 test failures
running post-clean rsync
These happen with or without my patches. And these does not fail on
x86_64 or AArch64.
Are these "only my" issue or you've seen them as well? Is there any
pointer to diagnose them?
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
reply other threads:[~2023-03-25 14:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3022ff730b2677f8bce36e48dd5aeb6c7bd6b93d.camel@xry111.site \
--to=xry111@xry111.site \
--cc=caiyinyu@loongson.cn \
--cc=i@xen0n.name \
--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).