diff options
| author | Robert Collins <robertc@robertcollins.net> | 2012-12-18 15:48:20 +1300 |
|---|---|---|
| committer | Robert Collins <robertc@robertcollins.net> | 2012-12-18 15:48:20 +1300 |
| commit | cc0e70a2955f2a0eab24c269d59f74a901dccf22 (patch) | |
| tree | df64e64575cc3dd00a5ad3b871e8e6a2119e5ffa /doc | |
| parent | ea8b9604170c560778cdbedab9be9b7469a6f64a (diff) | |
| download | testrepository-cc0e70a2955f2a0eab24c269d59f74a901dccf22.tar.gz | |
Document workaround.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/MANUAL.txt | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/MANUAL.txt b/doc/MANUAL.txt index f2f6c4a..595206f 100644 --- a/doc/MANUAL.txt +++ b/doc/MANUAL.txt @@ -159,7 +159,11 @@ 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. +is simple round-robin for tests that testr has not seen run before, and +equal-time buckets for tests that testr has seen run. NB: This uses the anydbm +Python module to store the duration of each test. On some platforms (to date +only OSX) there is no bulk-update API and performance may be impacted if you +have many (10's of thousands) of tests. 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 |