From f5a3328452884e6c954da1d26b59a3f2b035247d Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Fri, 10 Jul 2009 19:38:00 +0000 Subject: [PATCH] * gdbint.texinfo (Testsuite): Document parallel make check. --- gdb/doc/ChangeLog | 4 ++++ gdb/doc/gdbint.texinfo | 10 ++++++++++ 2 files changed, 14 insertions(+) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 1455a1e5f00..6842ec39ab1 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +2009-07-09 Tom Tromey + + * gdbint.texinfo (Testsuite): Document parallel make check. + 2009-07-09 Tom Tromey * gdbint.texinfo (Testsuite): Document test transcripts. diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index 3351a15fde4..b1c045218b4 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 -- 2.30.2