diff options
author | Thomas Rast <trast@inf.ethz.ch> | 2013-06-23 20:12:59 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-06-23 12:24:06 -0700 |
commit | ad0e6233320b004f0d686f6887c803e508607bd2 (patch) | |
tree | 92e9c9256b79904a8bc6c4e37c5aa0692d2ed83b /t/t5515/refs.br-remote-glob-merge | |
parent | test-lib: allow prefixing a custom string before "ok N" etc. (diff) | |
download | tgif-ad0e6233320b004f0d686f6887c803e508607bd2.tar.xz |
test-lib: support running tests under valgrind in parallel
With the new --valgrind-parallel=<n> option, we support running the
tests in a single test script under valgrind in parallel using 'n'
processes.
This really follows the dumbest approach possible, as follows:
* We spawn the test script 'n' times, using a throw-away
TEST_OUTPUT_DIRECTORY. Each of the instances is given options that
ensures that it only runs every n-th test under valgrind, but
together they cover the entire range.
* We add up the numbers from the individual tests, and provide the
usual output.
This is really a gross hack at this point, and should be improved. In
particular we should keep the actual outputs somewhere more easily
discoverable, and summarize them to the user.
Nevertheless, this is already workable and gives a speedup of more
than 2 on a dual-core (hyperthreaded) machine, using n=4. This is
expected since the overhead of valgrind is so big (on the order of 20x
under good conditions, and a large startup overhead at every git
invocation) that redundantly running the non-valgrind tests in between
is not that expensive.
Helped-by: Jeff King <peff@peff.net>
Signed-off-by: Thomas Rast <trast@inf.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/refs.br-remote-glob-merge')
0 files changed, 0 insertions, 0 deletions