summaryrefslogtreecommitdiffstats
path: root/contrib
diff options
context:
space:
mode:
authorLukas Slebodnik <lslebodn@redhat.com>2016-03-31 11:17:01 +0200
committerLukas Slebodnik <lslebodn@redhat.com>2016-04-01 09:45:17 +0200
commit5ebdc2391e96cfcc86ebdb8f223e159c00a0d82b (patch)
treefb6de09a29beb201b7fe33ecef926043f08b3cb6 /contrib
parentdad416a9b0095e1c423b7da65db7c636fa69e614 (diff)
downloadsssd-5ebdc2391e96cfcc86ebdb8f223e159c00a0d82b.tar.gz
sssd-5ebdc2391e96cfcc86ebdb8f223e159c00a0d82b.tar.xz
sssd-5ebdc2391e96cfcc86ebdb8f223e159c00a0d82b.zip
AUTOMAKE: Force usage of parallel test harness
Parallel test harness[1] is enabled by default with new versions of automake. However, automake on rhel6 (1.11.1-4) still uses serial test harness by default even though it also contains parallel test harness. Downside of serial test is that output of all test are mixed together and is not in separate log files as with parallel test harness. Another problem is slow execution test with valgrind due to missing parallelisation. It's approximately 4-5 minutes slower on machine with 4 CPUs. The automake option parallel-tests is kept for backward-compatibility in new versions of automake, since the parallel test harness is the default there. [1] http://www.gnu.org/software/automake/manual/html_node/Parallel-Test-Harness.html#Parallel-Test-Harness [2] http://www.gnu.org/software/automake/manual/html_node/Serial-Test-Harness.html#Serial-Test-Harness Reviewed-by: Nikolai Kondrashov <Nikolai.Kondrashov@redhat.com>
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions