| commit | b227bead4d8fb6e75b5c58ba511c7e935b09b24b | |
| author | brian m. carlson <sandals@crustytoothpaste.net> | |
| Wed, 11 Aug 2021 23:16:44 +0000 (11 23:16 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 12 Aug 2021 05:24:32 +0000 (11 22:24 -0700) | ||
| tree | 4a9425992ffb2818a667b192a3d535cf096ecbf6 | treesnapshot (tar.gz zip) |
| parent | 5d213e46bb7b880238ff5ea3914e940a50ae9369 | commitdiff |
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>
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>
| t/t5607-clone-bundle.sh | diffblobblamehistory |