This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Aarch64 test results and questions


Since we are in a freeze for 2.30, I ran the glibc tests on my aarch64
ThunderX2 box and was wondering if my results are consistent with what
other people are getting or not and if these failures need to be
investigated further.

I had to use Florian Weimer's patch to tst-pthread-getattr.c to get
that to build with the latest GCC.

After that I got four failures:

FAIL: elf/check-abi-libc
FAIL: elf/tst-ldconfig-bad-aux-cache
FAIL: elf/tst-pldd
FAIL: nss/tst-nss-files-hosts-long
      4 FAIL


check-abi-libc seems to be PR 14664

tst-nss-files-hosts-long may be PR 24816, I am not running in a docker,
I am on a native system.  The failure is:

	error: tst-nss-files-hosts-long.c:35: ahostsv4 failed
	error: 1 test failures

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

	tst-pldd.c:86: numeric comparison failure
	   left: -1 (0xffffffff); from: fscanf (out, "%u: " STRINPUT (512), &pid, buffer)
	  right: 2 (0x2); from: 2
	tst-pldd.c:88: numeric comparison failure
	   left: -1083244493 (0xbf6f0033); from: pid
	  right: 3 (0x3); from: target.pid
	tst-pldd.c:89: numeric comparison failure
	   left: -200 (0xffffff38); from: strcmp (basename (buffer), "tst-pldd")
	  right: 0 (0x0); from: 0
	tst-pldd.c:124: numeric comparison failure
	   left: 0 (0x0); from: interpreter_found
	  right: 1 (0x1); from: true
	tst-pldd.c:125: numeric comparison failure
	   left: 0 (0x0); from: libc_found
	  right: 1 (0x1); from: true
	error: 7 test failures

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


Steve Ellcey
sellcey@marvell.com

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]