This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RFA: update gdb internals doc with parallel make check
- From: Tom Tromey <tromey at redhat dot com>
- To: gdb-patches at sourceware dot org
- Date: Thu, 09 Jul 2009 10:36:31 -0600
- Subject: RFA: update gdb internals doc with parallel make check
- Reply-to: Tom Tromey <tromey at redhat dot com>
I noticed today that the db internals documentation has a section on
the test suite. This patch copies the parallel make check
documentation from README into the internals doc.
Please review.
Tom
2009-07-09 Tom Tromey <tromey@redhat.com>
* gdbint.texinfo (Testsuite): Document parallel make check.
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index a51f077..0a55e3a 100644
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -7519,6 +7519,16 @@ make check RUNTESTFLAGS='@var{tests}'
where @var{tests} is a list of test script file names, separated by
spaces.
+If you use GNU make, you can use its @code{-j} option to run the
+testsuite in parallel. This can greatly reduce the amount of time it
+takes for the testsuite to run. In this case, if you set
+@code{RUNTESTFLAGS} then, by default, the tests will be run serially
+even under @code{-j}. You can override this and force a parallel run
+by setting the @code{make} variable @code{FORCE_PARALLEL} to any
+non-empty value. Note that the parallel @code{make check} assumes
+that you want to run the entire testsuite, so it is not compatible
+with some dejagnu options, like @code{--directory}.
+
The ideal test run consists of expected passes only; however, reality
conspires to keep us from this ideal. Unexpected failures indicate
real problems, whether in @value{GDBN} or in the testsuite. Expected