summaryrefslogtreecommitdiff
path: root/t/t4018/python-async-def
diff options
context:
space:
mode:
authorLibravatar brian m. carlson <sandals@crustytoothpaste.net>2021-08-11 23:16:44 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-08-11 22:24:32 -0700
commitb227bead4d8fb6e75b5c58ba511c7e935b09b24b (patch)
tree4a9425992ffb2818a667b192a3d535cf096ecbf6 /t/t4018/python-async-def
parentGit 2.33-rc2 (diff)
downloadtgif-b227bead4d8fb6e75b5c58ba511c7e935b09b24b.tar.xz
t5607: avoid using prerequisites to select algorithm
In this test, we currently use the SHA1 prerequisite to specify the algorithm we're using to test, since SHA-256 bundles are always v3, whereas SHA-1 bundles default to v2, and as a result the default output differs. However, this causes a problem if we run with GIT_TEST_FAIL_PREREQS set, since that means that we'll unexpectedly fail the SHA1 prerequisite, resulting in incorrect expected output. Let's fix this by checking against the built-in data called "algo", which tells us which algorithm is in use. This should work in any situation, making our test a little more robust. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4018/python-async-def')
0 files changed, 0 insertions, 0 deletions