Bug 23887 - Testsuite fails posix/tst-spawn on ppc64 big-endian
Summary: Testsuite fails posix/tst-spawn on ppc64 big-endian
Status: RESOLVED INVALID
Alias: None
Product: glibc
Classification: Unclassified
Component: libc (show other bugs)
Version: 2.28
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL: https://buildd.debian.org/status/fetc...
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-15 11:51 UTC by John Paul Adrian Glaubitz
Modified: 2018-12-09 12:32 UTC (History)
4 users (show)

See Also:
Host:
Target: powerpc64-*-*
Build:
Last reconfirmed:
fweimer: security-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Paul Adrian Glaubitz 2018-11-15 11:51:07 UTC
Since 2.28, the testsuite is failing posix/tst-spawn on ppc64 big-endian with:

----------
FAIL: posix/tst-spawn
original exit status 1
error: tst-spawn.c:257: not true: WEXITSTATUS (status) == 0
error: 1 test failures
----------

Full log available at: https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=ppc64&ver=2.28-0experimental1&stamp=1542062050&raw=0

A POWER7 porterbox running Linux can be found in the gcc compile farm: https://cfarm.tetaneutral.net/machines/list/

If you need more input, please let me know.
Comment 2 John Paul Adrian Glaubitz 2018-11-15 12:28:43 UTC
(In reply to Andreas Schwab from comment #1)
> I don't see that here.
> 
> https://build.opensuse.org/package/live_build_log/Base:System/glibc:
> testsuite/openSUSE_Factory_PowerPC/ppc64

It's in the build log you linked:

[ 6408s] FAIL: misc/tst-pkey

Seems like the failure is not critical on openSUSE.
Comment 3 Andreas Schwab 2018-11-15 13:26:08 UTC
That doesn't match the subject.
Comment 4 John Paul Adrian Glaubitz 2018-11-15 13:28:59 UTC
(In reply to Andreas Schwab from comment #3)
> That doesn't match the subject.

Sorry, I got confused. You're right. posix/tst-spawn passes on openSUSE. This might be an artifact then which might be a problem with the setup of the machine.

I'll have another look and report back.
Comment 5 Andreas Schwab 2018-11-15 13:37:32 UTC
Do you have commit 1fe2b9ca8a?
Comment 7 John Paul Adrian Glaubitz 2018-11-15 17:20:43 UTC
Ok, looks like an artifact. I have given the glibc package back (Debian speak for initiating a rebuild attempt) and the testsuite failure no longer shows:

+---------------------------------------------------------------------+
|     Encountered regressions that don't match expected failures.     |
+---------------------------------------------------------------------+
FAIL: misc/tst-pkey
make: *** [debian/rules.d/build.mk:115: /<<PKGBUILDDIR>>/stamp-dir/check_libc] Error 1
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2

> https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=ppc64&ver=2.28-0experimental1&stamp=1542285400&raw=0

So, I guess we can close this as invalid. Thanks for checking the openSUSE side.