summaryrefslogtreecommitdiff
path: root/remote.h
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2011-06-17 16:36:32 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-06-17 13:48:53 -0700
commit36bfb0e5f6004e4c4ac9334107dc185c316839a7 (patch)
tree0d572261e1ef9c209be19a853be46124fd664f3a /remote.h
parentt/Makefile: pass test opts to valgrind target properly (diff)
downloadtgif-36bfb0e5f6004e4c4ac9334107dc185c316839a7.tar.xz
tests: link shell libraries into valgrind directory
When we run tests under valgrind, we symlink anything executable that starts with git-* or test-* into a special valgrind bin directory, and then make that our GIT_EXEC_PATH. However, shell libraries like git-sh-setup do not have the executable bit marked, and did not get symlinked. This means that any test looking for shell libraries in our exec-path would fail to find them, even though that is a fine thing to do when testing against a regular git build (or in a git install, for that matter). t2300 demonstrated this problem. The fix is to symlink these shell libraries directly into the valgrind directory. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'remote.h')
0 files changed, 0 insertions, 0 deletions