(unknown)
Ileana Dumitrescu <[email protected]>
| Newsgroups | gmane.comp.gnu.libtool.cvs |
|---|---|
| Message-ID | <[email protected]> |
branch: development commit 2048edd2cba086b194bd30901e5fe552a4890680 Author: Bruno Haible <[email protected]> AuthorDate: Tue May 14 13:25:51 2024 +0200 Document how to debug failing or skipped tests. * HACKING (Test Suite): Explain how to debug a range of tests. --- HACKING | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/HACKING b/HACKING index 20d65e9a..8eea9f7d 100644 --- a/HACKING +++ b/HACKING @@ -76,6 +76,12 @@ and is not part of a release distribution. AT_CHECK) is on a single line so that 'testsuite -x' displays the whole thing. You can use m4_do or '[... ]dnl' to wrap long lines. +* To debug a failing or skipped range of tests, e.g. 13 to 14: + make check-local TESTSUITEFLAGS="--debug 13-14" + More generally, in the TESTSUITEFLAGS you can use the documented + options for Autotest generated testsuites: + https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.72/html_node/testsuite-Invocation.html + * Run tests in parallel with make -k check TESTSUITEFLAGS="--jobs=$(nproc)" liberally, on as many platforms as you can. Use as many compilers and