2 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:52:38
Thomas Rast [off-list ref] writes:
The perf-lib work wants this feature, so we may as well do it for test-lib in general.
How is this different from what GIT_TEST_INSTALLED already gives us (other than "needs more diskspace to keep another source tree fully built", that is)?
From: Thomas Rast <hidden>
Date: 2016-06-15 22:52:38
On Wednesday 14 December 2011 19:07:35 Junio C Hamano wrote:
Thomas Rast [off-list ref] writes:quoted
The perf-lib work wants this feature, so we may as well do it for test-lib in general.How is this different from what GIT_TEST_INSTALLED already gives us (other than "needs more diskspace to keep another source tree fully built", that is)?
I was scared away by the note that it would use (among others) perl
libs from the current build tree. Upon investigation I also see that
the test-* situation is still not satisfactory. Some (like
test-chmtime) are used by the tests for a vital task, and if they ever
have to be fixed, we would want to use the fixed version in any "test
an old git" run. OTOH, others (e.g., test-dump-cache-tree) are linked
with the rest of the code and serve to test an otherwise not
accessible part of it, and testing an old git should use them from the
tested tree.
The disk space argument is moot IMO: for sane perf testing you need
the extra build tree anyway because you cannot checkout another
version in the current tree. Otherwise the scripts may change and/or
disappear from under themselves.
An optimization might be to have the run script only use a single
build tree and several install trees. However, while such a built
tree takes just over 100MB of space in my tests, everything installed
$PREFIX/libexec/git-core is also already 65MB here. So the latter
scheme would only amortize itself if you had at least 3 trees tested
simultaneously.
--
Thomas Rast
trast@{inf,student}.ethz.ch