From: Stefan Liebler <stli@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: nptl/tst-eintr1.c test question
Date: Fri, 16 Dec 2016 08:06:00 -0000 [thread overview]
Message-ID: <95615a2a-3189-f080-0b44-bae2fe8bd281@linux.vnet.ibm.com> (raw)
In-Reply-To: <201612152302.uBFN2dkC010965@sellcey-lt.caveonetworks.com>
On 12/16/2016 12:02 AM, Steve Ellcey wrote:
> I was wondering if anyone else is having problems with nptl/tst-eintr1?
> This test is known to fail on some kernels and there is a comment about
> it on the glibc wiki.
>
> https://sourceware.org/glibc/wiki/Testing/Testsuite#Known_testsuite_failures
>
> The problem I have is that when this test fails for me on my aarch64 box
> it doesn't just result in a failed test, it aborts the whole 'make check'
> process and I don't get any results printed out. I was wondering if there
> was some way to make this test not run on some platforms (and how I might
> identify what those platforms were).
>
> Maybe something like:
>
> #define BAD_KERNEL (defined (__ARM_ARCH_8A))
> #if BAD_KERNEL
> static int do_fail (void) { return 1; }
> # define TEST_FUNCTION do_fail ()
> #else
> # define TEST_FUNCTION do_test ()
> #endif
>
> I don't know if this test fails on all aarch8/8A platforms, I just know
> that it fails for me, so I am not sure what a good way to set BAD_KERNEL
> would be.
>
> Any thoughts?
>
> FYI: The failure I get is due to to many forks causing the make process(es) to
> abort:
>
> ../scripts/evaluate-test.sh nptl/tst-eintr1 $? false false > /home/ubuntu/sellcey/glibc-patched/obj-glibc64/nptl/tst-eintr1.test-result
> /bin/sh: 2: Cannot fork
> ../Rules:241: recipe for target '/home/ubuntu/sellcey/glibc-patched/obj-glibc64/nptl/tst-eintr1.out' failed
> make[2]: *** [/home/ubuntu/sellcey/glibc-patched/obj-glibc64/nptl/tst-eintr1.out] Error 2
> make[2]: Leaving directory '/home/ubuntu/sellcey/glibc-patched/src/glibc/nptl'
> Makefile:215: recipe for target 'nptl/tests' failed
> make[1]: *** [nptl/tests] Error 2
> make[1]: Leaving directory '/home/ubuntu/sellcey/glibc-patched/src/glibc'
> Makefile:9: recipe for target 'check' failed
> make: *** [check] Error 2
>
>
> Steve Ellcey
> sellcey@caviumnetworks.com
>
Hi Steve,
I recognize such EAGAIN failures on s390, too.
In my case, I can only see them if cgroups configuration has limited
pids.max. Otherwise, there is no issue.
If pthread_create fails with EAGAIN and I then query the number of
processes via e.g. sysinfo(), I recognize a small number of processes.
If I afterwards try pthread_create() again, it fails with EAGAIN, too.
The threads have been exited, but the kernel releases the PIDs only
interval-based. On at least s390 this interval is longer than on e.g. x86.
Bye
Stefan
prev parent reply other threads:[~2016-12-16 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 23:02 Steve Ellcey
2016-12-16 7:46 ` Florian Weimer
2016-12-16 8:06 ` Stefan Liebler [this message]
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=95615a2a-3189-f080-0b44-bae2fe8bd281@linux.vnet.ibm.com \
--to=stli@linux.vnet.ibm.com \
--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).