darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

* gdbint.texinfo (Testsuite): Document parallel make check.

Browse source
This commit is contained in:
Tom Tromey 2009-07-10 19:38:00 +00:00
parent 552deff831
commit f5a3328452
2 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gdb/doc/ChangeLog
View file

@ -1,3 +1,7 @@
2009-07-09 Tom Tromey <tromey@redhat.com>
* gdbint.texinfo (Testsuite): Document parallel make check.
2009-07-09 Tom Tromey <tromey@redhat.com> 2009-07-09 Tom Tromey <tromey@redhat.com>
* gdbint.texinfo (Testsuite): Document test transcripts. * gdbint.texinfo (Testsuite): Document test transcripts.

10
gdb/doc/gdbint.texinfo
View file

@ -7519,6 +7519,16 @@ make check RUNTESTFLAGS='@var{tests}'
where @var{tests} is a list of test script file names, separated by where @var{tests} is a list of test script file names, separated by
spaces. 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 The ideal test run consists of expected passes only; however, reality
conspires to keep us from this ideal. Unexpected failures indicate conspires to keep us from this ideal. Unexpected failures indicate
real problems, whether in @value{GDBN} or in the testsuite. Expected real problems, whether in @value{GDBN} or in the testsuite. Expected