This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Aarch64 test results and questions
- From: Florian Weimer <fweimer at redhat dot com>
- To: Steve Ellcey <sellcey at marvell dot com>
- Cc: "libc-alpha\@sourceware.org" <libc-alpha at sourceware dot org>
- Date: Fri, 26 Jul 2019 18:52:40 +0200
- Subject: Re: Aarch64 test results and questions
- References: <ff17c402f36f20d29b92e92cb58304d892e06e9c.camel@marvell.com>
* Steve Ellcey:
> tst-pldd does not seem to have any known PR associated with it. The
> .out file has:
>
> error: subprocess failed: pldd
> error: expected exit status: 0
> error: actual exit status: 1 [0x100]
> error: subprocess failed: pldd
> error: unexpected error output from subprocess
> /extra/sellcey/test-glibc/install/bin/pldd: cannot attach to process 3: Operation not permitted
pldd may not work at all on this platform due to YAMA ptrace scope
enforcement.
Maybe this is something we could detect in the test and use the
information to mark it UNSUPPORTED.
> tst-ldconfig-bad-aux-cache also does not seem to have any known PR's.
> I get the following in the .out file:
>
> tst-ldconfig-bad-aux-cache.c:84: numeric comparison failure
> left: 256 (0x100); from: status
> right: 0 (0x0); from: 0
> error: support-xstat.c:29: stat64 ("/var/cache/ldconfig/aux-cache"): No such file or directory
> error: 2 test failures
> running post-clean rsync
What's the path that ldconfig is actually creating on this target?
Thanks,
Florian