diff options
| author | Rubén Justo <rjusto@gmail.com> | 2024-07-11 23:10:51 +0900 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2024-07-11 08:37:44 -0700 |
| commit | 8c1d6691bc514e2c1c01a807e872b5dddcb2485b (patch) | |
| tree | df7132bbc2c5334255dc54ae82bafc51676ba229 /commit.c | |
| parent | test-lib: fix GIT_TEST_SANITIZE_LEAK_LOG (diff) | |
| download | git-8c1d6691bc514e2c1c01a807e872b5dddcb2485b.tar.gz 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 'commit.c')
0 files changed, 0 insertions, 0 deletions