summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2019-04-18 16:08:27 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-04-19 14:22:32 +0900
commitfe6f2b081fea2d1da16895102e3c61fc0e1bd733 (patch)
tree4c6bb7d4b65be7b99bc86b2a8c63512527bd4411 /Documentation
parentt5304: rename "sha1" variables to "oid" (diff)
downloadtgif-fe6f2b081fea2d1da16895102e3c61fc0e1bd733.tar.xz
t5304: add a test for pruning with bitmaps
Commit fde67d6896 (prune: use bitmaps for reachability traversal, 2019-02-13) uses bitmaps for pruning when they're available, but only covers this functionality in the t/perf tests. This makes a kind of sense, since the point is that the behaviour is indistinguishable before and after the patch, just faster. But since the bitmap code path is not exercised at all in the regular test suite, it leaves us open to a regression where the behavior does in fact change. The most thorough way to test that would be running the whole suite with bitmaps enabled. But we don't yet have a way to do that, and anyway it's expensive to do so. Let's at least add a basic test that exercises this path and make sure we prune an object we should (and not one that we shouldn't). That would hopefully catch the most obvious breakages early. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions