summaryrefslogtreecommitdiffstats
path: root/ci
diff options
context:
space:
mode:
authorRubén Justo <rjusto@gmail.com>2024-07-11 16:10:51 +0200
committerJunio C Hamano <gitster@pobox.com>2024-07-11 17:37:44 +0200
commit8c1d6691bc514e2c1c01a807e872b5dddcb2485b (patch)
treedf7132bbc2c5334255dc54ae82bafc51676ba229 /ci
parenttest-lib: fix GIT_TEST_SANITIZE_LEAK_LOG (diff)
downloadgit-8c1d6691bc514e2c1c01a807e872b5dddcb2485b.tar.xz
git-8c1d6691bc514e2c1c01a807e872b5dddcb2485b.zip
test-lib: GIT_TEST_SANITIZE_LEAK_LOG enabled by default
As we currently describe in t/README, it can happen that: Some tests run "git" (or "test-tool" etc.) without properly checking the exit code, or git will invoke itself and fail to ferry the abort() exit code to the original caller. Therefore, GIT_TEST_SANITIZE_LEAK_LOG=true is needed to be set to capture all memory leaks triggered by our tests. It seems unnecessary to force users to remember this option, as forgetting it could lead to missed memory leaks. We could solve the problem by making it "true" by default, but that might suggest we think "false" makes sense, which isn't the case. Therefore, the best approach is to remove the option entirely while maintaining the capability to detect memory leaks in blind spots of our tests. Signed-off-by: Rubén Justo <rjusto@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'ci')
-rwxr-xr-xci/lib.sh1
1 files changed, 0 insertions, 1 deletions
diff --git a/ci/lib.sh b/ci/lib.sh
index ff66ad356b..fe52954828 100755
--- a/ci/lib.sh
+++ b/ci/lib.sh
@@ -374,7 +374,6 @@ linux-musl)
linux-leaks|linux-reftable-leaks)
export SANITIZE=leak
export GIT_TEST_PASSING_SANITIZE_LEAK=true
- export GIT_TEST_SANITIZE_LEAK_LOG=true
;;
linux-asan-ubsan)
export SANITIZE=address,undefined