This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
How to handle long running tests in nptl.
- From: Stefan Liebler <stli at linux dot ibm dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 12 Sep 2019 15:21:44 +0200
- Subject: How to handle long running tests in nptl.
Hi,
the nptl tests are currently running in sequence. Some of them are
running very long:
-tst-cond16: 20s
-tst-cond17: 20s
-tst-cond18: 20s
-tst-rwlock-tryrdlock-stall: 20s
-tst-mutex10: 16s
-tst-rwlock20: 10s
-tst-rwlock-trywrlock-stall: 10s
-tst-rwlock-pwn: 10s
The listed tests are responsible for over two minutes of runtime of
"make check". They all are running a test in a loop for a large amount
of iterations or seconds in order to trigger e.g. a race condition.
How to handle those long running tests with respect of "make check" runtime?
- reduce runtime by reducing number of iterations or seconds
- move those tests to "make xcheck"
- reduce runtime while running "make check" and rerun with unchanged
runtime in "make xcheck"
- change nothing
- other ideas?
Bye,
Stefan