diff options
| author | Robert Collins <robertc@robertcollins.net> | 2012-06-18 14:21:14 +1200 |
|---|---|---|
| committer | Robert Collins <robertc@robertcollins.net> | 2012-06-18 14:21:14 +1200 |
| commit | 5a1b7e516a28cd7425a704065ce5ffe44673ba36 (patch) | |
| tree | 60741e5bc3552e6703592bea3b0eb63054f26422 /doc | |
| parent | 38a5132cab329f3dcb852b068c32ec444ab24e58 (diff) | |
| download | testrepository-5a1b7e516a28cd7425a704065ce5ffe44673ba36.tar.gz | |
* ``testr run`` now accepts a --concurrency option, allowing command line
override of the number of workers spawned. This allows conccurency on
operating systems where autodetection is not yet implemented, or just
debugging problems with concurrent test suites. (Robert Collins, #957145)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/MANUAL.txt | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/MANUAL.txt b/doc/MANUAL.txt index d925fb6..566d47e 100644 --- a/doc/MANUAL.txt +++ b/doc/MANUAL.txt @@ -96,7 +96,15 @@ then testr is able to run your tests in parallel:: This will first list the tests, partition the tests into one partition per CPU on the machine, and then invoke multiple test runners at the same time, with each test runner getting one partition. Currently the partitioning algorithm -is a simple round-robin, and the CPU detection is only implemented for Linux. +is a simple round-robin. + +On Linux, testrepository will inspect /proc/cpuinfo to determine how many CPUs +are present in the machine, and run one worker per CPU. On other operating +systems, or if you need to control the number of workers that are used, the +--concurrency option will let you do so:: + + $ testr run --parallel --concurrency=2 + Hiding tests ~~~~~~~~~~~~ |