path: root/t/
diff options
authorÆvar Arnfjörð Bjarmason <>2022-04-13 20:01:48 (GMT)
committerJunio C Hamano <>2022-04-14 06:56:09 (GMT)
commite75d2f7f73420884c50613a8242812b55ad2a8fa (patch)
treefe61a8999ccca411e2f50f03750383dace090948 /t/
parent7a98d9ab00dc0a238b624b20c3884b50fe504e2b (diff)
revisions API: have release_revisions() release "filter"
Extend the the release_revisions() function so that it frees the "filter" in the "struct rev_info". This in combination with a preceding change to free "cmdline" means that we can mark another set of tests as passing under "TEST_PASSES_SANITIZE_LEAK=true". The "filter" member was added recently in ffaa137f646 (revision: put object filter into struct rev_info, 2022-03-09), and this fixes leaks intruded in the subsequent leak 7940941de1f (pack-objects: use rev.filter when possible, 2022-03-09) and 105c6f14ad3 (bundle: parse filter capability, 2022-03-09). The "builtin/pack-objects.c" leak in 7940941de1f was effectively with us already, but the variable was referred to by a "static" file-scoped variable. The "bundle.c " leak in 105c6f14ad3 was newly introduced with the new "filter" feature for bundles. The "" change here to add "TEST_PASSES_SANITIZE_LEAK=true" is one of the cases where run-command.c in not carrying the abort() exit code upwards would have had that test passing before, but now it *actually* passes[1]. We should fix the lack of 1=1 mapping of SANITIZE=leak testing to actual leaks some other time, but it's an existing edge case, let's just mark the really-passing test as passing for now. 1. Signed-off-by: Ævar Arnfjörð Bjarmason <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 't/')
1 files changed, 2 insertions, 0 deletions
diff --git a/t/ b/t/
index e904500..eb4ef3d 100755
--- a/t/
+++ b/t/
@@ -1,6 +1,8 @@
test_description='pack-objects breaks long cross-pack delta chains'
. ./
# This mirrors a repeated push setup: