* linknamespace failures with massively parallel builds
@ 2015-05-21 16:36 Florian Weimer
2015-05-21 20:17 ` Carlos O'Donell
0 siblings, 1 reply; 2+ messages in thread
From: Florian Weimer @ 2015-05-21 16:36 UTC (permalink / raw)
To: GNU C Library
I see a lot of failures when running make check with large -j numbers
(on hardware which has a matching number of threads). Here are some
example:
FAIL: conform/XPG4/setjmp.h/linknamespace
FAIL: conform/XPG4/signal.h/linknamespace
FAIL: conform/XPG4/string.h/linknamespace
FAIL: conform/XPG4/strings.h/linknamespace
FAIL: conform/XPG4/stropts.h/linknamespace
FAIL: conform/XPG4/sys/ipc.h/linknamespace
FAIL: conform/XPG4/sys/mman.h/linknamespace
FAIL: conform/XPG4/sys/msg.h/linknamespace
Does anyone else see this?
linknamespace.pl exits with 1, with the following output:
==> conform/XPG4/termios.h/linknamespace.out <==
[initial] cfgetispeed
[initial] cfgetospeed
[initial] cfsetispeed
[initial] cfsetospeed
[initial] cfgetispeed -> [libc.a(speed.o)] __libc_errno ->
[libc.a(errno.o)] errno
[initial] tcdrain
[initial] tcflow
[initial] tcflush
[initial] tcgetattr
[initial] tcsendbreak
[initial] tcsetattr
==> conform/XPG4/termios.h/linknamespace.test-result <==
FAIL: conform/XPG4/termios.h/linknamespace
original exit status 1
I looked for file system races as an explanation, but I don't see them.
--
Florian Weimer / Red Hat Product Security
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: linknamespace failures with massively parallel builds
2015-05-21 16:36 linknamespace failures with massively parallel builds Florian Weimer
@ 2015-05-21 20:17 ` Carlos O'Donell
0 siblings, 0 replies; 2+ messages in thread
From: Carlos O'Donell @ 2015-05-21 20:17 UTC (permalink / raw)
To: Florian Weimer, GNU C Library
On 05/21/2015 12:07 PM, Florian Weimer wrote:
> I see a lot of failures when running make check with large -j numbers
> (on hardware which has a matching number of threads). Here are some
> example:
>
> FAIL: conform/XPG4/setjmp.h/linknamespace
> FAIL: conform/XPG4/signal.h/linknamespace
> FAIL: conform/XPG4/string.h/linknamespace
> FAIL: conform/XPG4/strings.h/linknamespace
> FAIL: conform/XPG4/stropts.h/linknamespace
> FAIL: conform/XPG4/sys/ipc.h/linknamespace
> FAIL: conform/XPG4/sys/mman.h/linknamespace
> FAIL: conform/XPG4/sys/msg.h/linknamespace
>
> Does anyone else see this?
>
> linknamespace.pl exits with 1, with the following output:
>
> ==> conform/XPG4/termios.h/linknamespace.out <==
> [initial] cfgetispeed
> [initial] cfgetospeed
> [initial] cfsetispeed
> [initial] cfsetospeed
> [initial] cfgetispeed -> [libc.a(speed.o)] __libc_errno ->
> [libc.a(errno.o)] errno
> [initial] tcdrain
> [initial] tcflow
> [initial] tcflush
> [initial] tcgetattr
> [initial] tcsendbreak
> [initial] tcsetattr
>
> ==> conform/XPG4/termios.h/linknamespace.test-result <==
> FAIL: conform/XPG4/termios.h/linknamespace
> original exit status 1
>
> I looked for file system races as an explanation, but I don't see them.
I've never seen this failure. What is large -j? How many cpus?
I'll try to reproduce.
c.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-05-21 17:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-21 16:36 linknamespace failures with massively parallel builds Florian Weimer
2015-05-21 20:17 ` Carlos O'Donell
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).