aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc/gdbint.texinfo
diff options
context:
space:
mode:
authorTom Tromey <tromey@redhat.com>2009-07-10 19:38:00 +0000
committerTom Tromey <tromey@redhat.com>2009-07-10 19:38:00 +0000
commitf5a3328452884e6c954da1d26b59a3f2b035247d (patch)
tree1d9aa0616923fe755973b69b9ff0d4d1207e5de5 /gdb/doc/gdbint.texinfo
parent552deff83171bdf238eacd1cc2798ca8bc849093 (diff)
downloadgdb-f5a3328452884e6c954da1d26b59a3f2b035247d.zip
gdb-f5a3328452884e6c954da1d26b59a3f2b035247d.tar.gz
gdb-f5a3328452884e6c954da1d26b59a3f2b035247d.tar.bz2
* gdbint.texinfo (Testsuite): Document parallel make check.
Diffstat (limited to 'gdb/doc/gdbint.texinfo')
-rw-r--r--gdb/doc/gdbint.texinfo10
1 files changed, 10 insertions, 0 deletions
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index 3351a15..b1c0452 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 @option{-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 @option{-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 @kbd{make check} assumes
+that you want to run the entire testsuite, so it is not compatible
+with some dejagnu options, like @option{--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