This is the mail archive of the
mailing list for the glibc project.
Re: How to handle long running tests in nptl.
- From: Cyril Hrubis <chrubis at suse dot cz>
- To: Stefan Liebler <stli at linux dot ibm dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 13 Sep 2019 16:32:01 +0200
- Subject: Re: How to handle long running tests in nptl.
- References: <email@example.com>
> 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?
We do have a nice fuzzy sync library in LTP that is designed especially
to trigger race conditions, which was developed to speed up LTP CVE
related tests. With this library runtime for race test can usually be
reduced from minutes to couple of seconds.
We also plan to prepare a talk about this library for next FOSDEM in
order to spare people from reinventing the wheel again and again.