2005-06-26 15:29:18 +04:00
|
|
|
#!/bin/sh
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2005 Junio C Hamano
|
|
|
|
|
#
|
|
|
|
|
|
2008-09-03 12:59:29 +04:00
|
|
|
test_description='git pack-object
|
2005-06-26 15:29:18 +04:00
|
|
|
|
|
|
|
|
'
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_expect_success 'setup' '
|
|
|
|
|
rm -f .git/index* &&
|
|
|
|
|
perl -e "print \"a\" x 4096;" >a &&
|
|
|
|
|
perl -e "print \"b\" x 4096;" >b &&
|
|
|
|
|
perl -e "print \"c\" x 4096;" >c &&
|
|
|
|
|
test-tool genrandom "seed a" 2097152 >a_big &&
|
|
|
|
|
test-tool genrandom "seed b" 2097152 >b_big &&
|
|
|
|
|
git update-index --add a a_big b b_big c &&
|
|
|
|
|
cat c >d && echo foo >>d && git update-index --add d &&
|
|
|
|
|
tree=$(git write-tree) &&
|
|
|
|
|
commit=$(git commit-tree $tree </dev/null) &&
|
|
|
|
|
{
|
|
|
|
|
echo $tree &&
|
|
|
|
|
echo $commit &&
|
|
|
|
|
git ls-tree $tree | sed -e "s/.* \\([0-9a-f]*\\) .*/\\1/"
|
|
|
|
|
} >obj-list &&
|
|
|
|
|
{
|
|
|
|
|
git diff-tree --root -p $commit &&
|
|
|
|
|
while read object
|
|
|
|
|
do
|
|
|
|
|
t=$(git cat-file -t $object) &&
|
|
|
|
|
git cat-file $t $object || return 1
|
|
|
|
|
done <obj-list
|
|
|
|
|
} >expect
|
|
|
|
|
'
|
2005-06-26 15:29:18 +04:00
|
|
|
|
2021-06-21 18:03:37 +03:00
|
|
|
test_expect_success 'setup pack-object <stdin' '
|
|
|
|
|
git init pack-object-stdin &&
|
|
|
|
|
test_commit -C pack-object-stdin one &&
|
|
|
|
|
test_commit -C pack-object-stdin two
|
|
|
|
|
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'pack-object <stdin parsing: basic [|--revs]' '
|
|
|
|
|
cat >in <<-EOF &&
|
|
|
|
|
$(git -C pack-object-stdin rev-parse one)
|
|
|
|
|
EOF
|
|
|
|
|
|
|
|
|
|
git -C pack-object-stdin pack-objects basic-stdin <in &&
|
|
|
|
|
idx=$(echo pack-object-stdin/basic-stdin-*.idx) &&
|
|
|
|
|
git show-index <"$idx" >actual &&
|
|
|
|
|
test_line_count = 1 actual &&
|
|
|
|
|
|
|
|
|
|
git -C pack-object-stdin pack-objects --revs basic-stdin-revs <in &&
|
|
|
|
|
idx=$(echo pack-object-stdin/basic-stdin-revs-*.idx) &&
|
|
|
|
|
git show-index <"$idx" >actual &&
|
|
|
|
|
test_line_count = 3 actual
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'pack-object <stdin parsing: [|--revs] bad line' '
|
|
|
|
|
cat >in <<-EOF &&
|
|
|
|
|
$(git -C pack-object-stdin rev-parse one)
|
|
|
|
|
garbage
|
|
|
|
|
$(git -C pack-object-stdin rev-parse two)
|
|
|
|
|
EOF
|
|
|
|
|
|
|
|
|
|
sed "s/^> //g" >err.expect <<-EOF &&
|
|
|
|
|
fatal: expected object ID, got garbage:
|
|
|
|
|
> garbage
|
|
|
|
|
|
|
|
|
|
EOF
|
|
|
|
|
test_must_fail git -C pack-object-stdin pack-objects bad-line-stdin <in 2>err.actual &&
|
|
|
|
|
test_cmp err.expect err.actual &&
|
|
|
|
|
|
|
|
|
|
cat >err.expect <<-EOF &&
|
|
|
|
|
fatal: bad revision '"'"'garbage'"'"'
|
|
|
|
|
EOF
|
|
|
|
|
test_must_fail git -C pack-object-stdin pack-objects --revs bad-line-stdin-revs <in 2>err.actual &&
|
|
|
|
|
test_cmp err.expect err.actual
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'pack-object <stdin parsing: [|--revs] empty line' '
|
|
|
|
|
cat >in <<-EOF &&
|
|
|
|
|
$(git -C pack-object-stdin rev-parse one)
|
|
|
|
|
|
|
|
|
|
$(git -C pack-object-stdin rev-parse two)
|
|
|
|
|
EOF
|
|
|
|
|
|
|
|
|
|
sed -e "s/^> //g" -e "s/Z$//g" >err.expect <<-EOF &&
|
|
|
|
|
fatal: expected object ID, got garbage:
|
|
|
|
|
> Z
|
|
|
|
|
|
|
|
|
|
EOF
|
|
|
|
|
test_must_fail git -C pack-object-stdin pack-objects empty-line-stdin <in 2>err.actual &&
|
|
|
|
|
test_cmp err.expect err.actual &&
|
|
|
|
|
|
|
|
|
|
git -C pack-object-stdin pack-objects --revs empty-line-stdin-revs <in &&
|
|
|
|
|
idx=$(echo pack-object-stdin/empty-line-stdin-revs-*.idx) &&
|
|
|
|
|
git show-index <"$idx" >actual &&
|
|
|
|
|
test_line_count = 3 actual
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'pack-object <stdin parsing: [|--revs] with --stdin' '
|
|
|
|
|
cat >in <<-EOF &&
|
|
|
|
|
$(git -C pack-object-stdin rev-parse one)
|
|
|
|
|
$(git -C pack-object-stdin rev-parse two)
|
|
|
|
|
EOF
|
|
|
|
|
|
|
|
|
|
# There is the "--stdin-packs is incompatible with --revs"
|
|
|
|
|
# test below, but we should make sure that the revision.c
|
|
|
|
|
# --stdin is not picked up
|
|
|
|
|
cat >err.expect <<-EOF &&
|
|
|
|
|
fatal: disallowed abbreviated or ambiguous option '"'"'stdin'"'"'
|
|
|
|
|
EOF
|
|
|
|
|
test_must_fail git -C pack-object-stdin pack-objects stdin-with-stdin-option --stdin <in 2>err.actual &&
|
|
|
|
|
test_cmp err.expect err.actual &&
|
|
|
|
|
|
|
|
|
|
test_must_fail git -C pack-object-stdin pack-objects --stdin --revs stdin-with-stdin-option-revs 2>err.actual <in &&
|
|
|
|
|
test_cmp err.expect err.actual
|
|
|
|
|
'
|
|
|
|
|
|
2021-07-09 13:13:48 +03:00
|
|
|
test_expect_success 'pack-object <stdin parsing: --stdin-packs handles garbage' '
|
|
|
|
|
cat >in <<-EOF &&
|
|
|
|
|
$(git -C pack-object-stdin rev-parse one)
|
|
|
|
|
$(git -C pack-object-stdin rev-parse two)
|
|
|
|
|
EOF
|
|
|
|
|
|
|
|
|
|
# That we get "two" and not "one" has to do with OID
|
|
|
|
|
# ordering. It happens to be the same here under SHA-1 and
|
|
|
|
|
# SHA-256. See commentary in pack-objects.c
|
|
|
|
|
cat >err.expect <<-EOF &&
|
|
|
|
|
fatal: could not find pack '"'"'$(git -C pack-object-stdin rev-parse two)'"'"'
|
|
|
|
|
EOF
|
|
|
|
|
test_must_fail git \
|
|
|
|
|
-C pack-object-stdin \
|
|
|
|
|
pack-objects stdin-with-stdin-option --stdin-packs \
|
|
|
|
|
<in 2>err.actual &&
|
|
|
|
|
test_cmp err.expect err.actual
|
|
|
|
|
'
|
|
|
|
|
|
2021-05-01 17:03:25 +03:00
|
|
|
# usage: check_deltas <stderr_from_pack_objects> <cmp_op> <nr_deltas>
|
|
|
|
|
# e.g.: check_deltas stderr -gt 0
|
|
|
|
|
check_deltas() {
|
|
|
|
|
deltas=$(perl -lne '/delta (\d+)/ and print $1' "$1") &&
|
|
|
|
|
shift &&
|
|
|
|
|
if ! test "$deltas" "$@"
|
|
|
|
|
then
|
|
|
|
|
echo >&2 "unexpected number of deltas (compared $delta $*)"
|
|
|
|
|
return 1
|
|
|
|
|
fi
|
|
|
|
|
}
|
|
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_expect_success 'pack without delta' '
|
2021-05-01 17:03:25 +03:00
|
|
|
packname_1=$(git pack-objects --progress --window=0 test-1 \
|
|
|
|
|
<obj-list 2>stderr) &&
|
|
|
|
|
check_deltas stderr = 0
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
'
|
2005-06-26 15:29:18 +04:00
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_expect_success 'pack-objects with bogus arguments' '
|
|
|
|
|
test_must_fail git pack-objects --window=0 test-1 blah blah <obj-list
|
|
|
|
|
'
|
2005-06-26 15:29:18 +04:00
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
check_unpack () {
|
2022-04-05 08:20:16 +03:00
|
|
|
local packname="$1" &&
|
|
|
|
|
local object_list="$2" &&
|
|
|
|
|
local git_config="$3" &&
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_when_finished "rm -rf git2" &&
|
2022-04-05 08:20:16 +03:00
|
|
|
git $git_config init --bare git2 &&
|
|
|
|
|
(
|
|
|
|
|
git $git_config -C git2 unpack-objects -n <"$packname".pack &&
|
|
|
|
|
git $git_config -C git2 unpack-objects <"$packname".pack &&
|
|
|
|
|
git $git_config -C git2 cat-file --batch-check="%(objectname)"
|
|
|
|
|
) <"$object_list" >current &&
|
|
|
|
|
cmp "$object_list" current
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
test_expect_success 'unpack without delta' '
|
2022-04-05 08:20:16 +03:00
|
|
|
check_unpack test-1-${packname_1} obj-list
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
BATCH_CONFIGURATION='-c core.fsync=loose-object -c core.fsyncmethod=batch'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'unpack without delta (core.fsyncmethod=batch)' '
|
|
|
|
|
check_unpack test-1-${packname_1} obj-list "$BATCH_CONFIGURATION"
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
'
|
2005-06-26 15:29:18 +04:00
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_expect_success 'pack with REF_DELTA' '
|
2021-05-01 17:03:25 +03:00
|
|
|
packname_2=$(git pack-objects --progress test-2 <obj-list 2>stderr) &&
|
|
|
|
|
check_deltas stderr -gt 0
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
'
|
2005-06-26 15:29:18 +04:00
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_expect_success 'unpack with REF_DELTA' '
|
2022-04-05 08:20:16 +03:00
|
|
|
check_unpack test-2-${packname_2} obj-list
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'unpack with REF_DELTA (core.fsyncmethod=batch)' '
|
|
|
|
|
check_unpack test-2-${packname_2} obj-list "$BATCH_CONFIGURATION"
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
'
|
2007-03-16 20:50:18 +03:00
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_expect_success 'pack with OFS_DELTA' '
|
2021-05-01 17:03:25 +03:00
|
|
|
packname_3=$(git pack-objects --progress --delta-base-offset test-3 \
|
|
|
|
|
<obj-list 2>stderr) &&
|
|
|
|
|
check_deltas stderr -gt 0
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
'
|
2007-03-16 20:50:18 +03:00
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_expect_success 'unpack with OFS_DELTA' '
|
2022-04-05 08:20:16 +03:00
|
|
|
check_unpack test-3-${packname_3} obj-list
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'unpack with OFS_DELTA (core.fsyncmethod=batch)' '
|
2023-05-18 23:03:20 +03:00
|
|
|
check_unpack test-3-${packname_3} obj-list "$BATCH_CONFIGURATION"
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
'
|
2007-03-16 20:50:18 +03:00
|
|
|
|
2007-04-07 03:49:03 +04:00
|
|
|
test_expect_success 'compare delta flavors' '
|
2013-10-29 05:23:03 +04:00
|
|
|
perl -e '\''
|
2007-04-07 03:49:03 +04:00
|
|
|
defined($_ = -s $_) or die for @ARGV;
|
|
|
|
|
exit 1 if $ARGV[0] <= $ARGV[1];
|
|
|
|
|
'\'' test-2-$packname_2.pack test-3-$packname_3.pack
|
|
|
|
|
'
|
2007-03-16 20:50:18 +03:00
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
check_use_objects () {
|
|
|
|
|
test_when_finished "rm -rf git2" &&
|
|
|
|
|
git init --bare git2 &&
|
|
|
|
|
cp "$1".pack "$1".idx git2/objects/pack &&
|
|
|
|
|
(
|
|
|
|
|
cd git2 &&
|
|
|
|
|
git diff-tree --root -p $commit &&
|
|
|
|
|
while read object
|
|
|
|
|
do
|
|
|
|
|
t=$(git cat-file -t $object) &&
|
|
|
|
|
git cat-file $t $object || exit 1
|
|
|
|
|
done
|
|
|
|
|
) <obj-list >current &&
|
|
|
|
|
cmp expect current
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
test_expect_success 'use packed objects' '
|
|
|
|
|
check_use_objects test-1-${packname_1}
|
|
|
|
|
'
|
2005-06-27 14:35:33 +04:00
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_expect_success 'use packed deltified (REF_DELTA) objects' '
|
|
|
|
|
check_use_objects test-2-${packname_2}
|
|
|
|
|
'
|
2005-06-27 14:35:33 +04:00
|
|
|
|
t5300: modernize basic tests
The first set of tests in t5300 goes back to 2005, and doesn't use some
of our customary style and tools these days. In preparation for touching
them, let's modernize a few things:
- titles go on the line with test_expect_success, with a hanging
open-quote to start the test body
- test bodies should be indented with tabs
- opening braces for shell blocks in &&-chains go on their own line
- no space between redirect operators and files (">foo", not "> foo")
- avoid doing work outside of test blocks; in this case, we can stick
the setup of ".git2" into the appropriate blocks
- avoid modifying and then cleaning up the environment or current
directory by using subshells and "git -C"
- this test does a curious thing when testing the unpacking: it sets
GIT_OBJECT_DIRECTORY, and then does a "git init" in the _original_
directory, creating a weird mixed situation. Instead, it's much
simpler to just "git init --bare" a new repository to unpack into,
and check the results there. I renamed this "git2" instead of
".git2" to make it more clear it's a separate repo.
- we can observe that the bodies of the no-delta, ref_delta, and
ofs_delta cases are all virtually identical except for the pack
creation, and factor out shared helper functions. I collapsed "do
the unpack" and "check the results of the unpack" into a single
test, since that makes the expected lifetime of the "git2" temporary
directory more clear (that also lets us use test_when_finished to
clean it up). This does make the "-v" output slightly less useful,
but the improvement in reading the actual test code makes it worth
it.
- I dropped the "pwd" calls from some tests. These don't do anything
functional, and I suspect may have been an aid for debugging when
the script was more cavalier about leaving the working directory
changed between tests.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-01 17:02:59 +03:00
|
|
|
test_expect_success 'use packed deltified (OFS_DELTA) objects' '
|
|
|
|
|
check_use_objects test-3-${packname_3}
|
|
|
|
|
'
|
2005-06-29 13:51:27 +04:00
|
|
|
|
2009-02-25 10:11:29 +03:00
|
|
|
test_expect_success 'survive missing objects/pack directory' '
|
|
|
|
|
(
|
|
|
|
|
rm -fr missing-pack &&
|
|
|
|
|
mkdir missing-pack &&
|
|
|
|
|
cd missing-pack &&
|
|
|
|
|
git init &&
|
2018-07-02 03:24:01 +03:00
|
|
|
GOP=.git/objects/pack &&
|
2009-02-25 10:11:29 +03:00
|
|
|
rm -fr $GOP &&
|
|
|
|
|
git index-pack --stdin --keep=test <../test-3-${packname_3}.pack &&
|
|
|
|
|
test -f $GOP/pack-${packname_3}.pack &&
|
2013-10-26 23:17:14 +04:00
|
|
|
cmp $GOP/pack-${packname_3}.pack ../test-3-${packname_3}.pack &&
|
2009-02-25 10:11:29 +03:00
|
|
|
test -f $GOP/pack-${packname_3}.idx &&
|
2013-10-26 23:17:14 +04:00
|
|
|
cmp $GOP/pack-${packname_3}.idx ../test-3-${packname_3}.idx &&
|
2009-02-25 10:11:29 +03:00
|
|
|
test -f $GOP/pack-${packname_3}.keep
|
|
|
|
|
)
|
|
|
|
|
'
|
|
|
|
|
|
2023-05-18 23:03:20 +03:00
|
|
|
test_expect_success 'verify pack' '
|
|
|
|
|
git verify-pack test-1-${packname_1}.idx \
|
|
|
|
|
test-2-${packname_2}.idx \
|
|
|
|
|
test-3-${packname_3}.idx
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'verify pack -v' '
|
|
|
|
|
git verify-pack -v test-1-${packname_1}.idx \
|
|
|
|
|
test-2-${packname_2}.idx \
|
|
|
|
|
test-3-${packname_3}.idx
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'verify-pack catches mismatched .idx and .pack files' '
|
|
|
|
|
cat test-1-${packname_1}.idx >test-3.idx &&
|
|
|
|
|
cat test-2-${packname_2}.pack >test-3.pack &&
|
|
|
|
|
if git verify-pack test-3.idx
|
|
|
|
|
then false
|
|
|
|
|
else :;
|
|
|
|
|
fi
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'verify-pack catches a corrupted pack signature' '
|
|
|
|
|
cat test-1-${packname_1}.pack >test-3.pack &&
|
|
|
|
|
echo | dd of=test-3.pack count=1 bs=1 conv=notrunc seek=2 &&
|
|
|
|
|
if git verify-pack test-3.idx
|
|
|
|
|
then false
|
|
|
|
|
else :;
|
|
|
|
|
fi
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'verify-pack catches a corrupted pack version' '
|
|
|
|
|
cat test-1-${packname_1}.pack >test-3.pack &&
|
|
|
|
|
echo | dd of=test-3.pack count=1 bs=1 conv=notrunc seek=7 &&
|
|
|
|
|
if git verify-pack test-3.idx
|
|
|
|
|
then false
|
|
|
|
|
else :;
|
|
|
|
|
fi
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'verify-pack catches a corrupted type/size of the 1st packed object data' '
|
|
|
|
|
cat test-1-${packname_1}.pack >test-3.pack &&
|
|
|
|
|
echo | dd of=test-3.pack count=1 bs=1 conv=notrunc seek=12 &&
|
|
|
|
|
if git verify-pack test-3.idx
|
|
|
|
|
then false
|
|
|
|
|
else :;
|
|
|
|
|
fi
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'verify-pack catches a corrupted sum of the index file itself' '
|
|
|
|
|
l=$(wc -c <test-3.idx) &&
|
|
|
|
|
l=$(expr $l - 20) &&
|
|
|
|
|
cat test-1-${packname_1}.pack >test-3.pack &&
|
|
|
|
|
printf "%20s" "" | dd of=test-3.idx count=20 bs=1 conv=notrunc seek=$l &&
|
|
|
|
|
if git verify-pack test-3.pack
|
|
|
|
|
then false
|
|
|
|
|
else :;
|
|
|
|
|
fi
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'build pack index for an existing pack' '
|
|
|
|
|
cat test-1-${packname_1}.pack >test-3.pack &&
|
|
|
|
|
git index-pack -o tmp.idx test-3.pack &&
|
|
|
|
|
cmp tmp.idx test-1-${packname_1}.idx &&
|
|
|
|
|
|
|
|
|
|
git index-pack --promisor=message test-3.pack &&
|
|
|
|
|
cmp test-3.idx test-1-${packname_1}.idx &&
|
|
|
|
|
echo message >expect &&
|
|
|
|
|
test_cmp expect test-3.promisor &&
|
|
|
|
|
|
|
|
|
|
cat test-2-${packname_2}.pack >test-3.pack &&
|
|
|
|
|
git index-pack -o tmp.idx test-2-${packname_2}.pack &&
|
|
|
|
|
cmp tmp.idx test-2-${packname_2}.idx &&
|
|
|
|
|
|
|
|
|
|
git index-pack test-3.pack &&
|
|
|
|
|
cmp test-3.idx test-2-${packname_2}.idx &&
|
|
|
|
|
|
|
|
|
|
cat test-3-${packname_3}.pack >test-3.pack &&
|
|
|
|
|
git index-pack -o tmp.idx test-3-${packname_3}.pack &&
|
|
|
|
|
cmp tmp.idx test-3-${packname_3}.idx &&
|
|
|
|
|
|
|
|
|
|
git index-pack test-3.pack &&
|
|
|
|
|
cmp test-3.idx test-3-${packname_3}.idx &&
|
|
|
|
|
|
|
|
|
|
cat test-1-${packname_1}.pack >test-4.pack &&
|
|
|
|
|
rm -f test-4.keep &&
|
|
|
|
|
git index-pack --keep=why test-4.pack &&
|
|
|
|
|
cmp test-1-${packname_1}.idx test-4.idx &&
|
|
|
|
|
test -f test-4.keep &&
|
|
|
|
|
|
|
|
|
|
:
|
|
|
|
|
'
|
2005-10-12 23:01:31 +04:00
|
|
|
|
2023-08-25 16:58:27 +03:00
|
|
|
# The `--rev-index` option of `git index-pack` is now the default, so
|
|
|
|
|
# a `foo.rev` REV file will be created when a `foo.idx` IDX file is
|
|
|
|
|
# created. Normally, these pathnames are based upon the `foo.pack`
|
|
|
|
|
# PACK file pathname.
|
|
|
|
|
#
|
|
|
|
|
# However, the `-o` option lets you set the pathname of the IDX file
|
|
|
|
|
# indepdent of the PACK file.
|
|
|
|
|
#
|
|
|
|
|
# Verify what happens if these suffixes are changed.
|
|
|
|
|
#
|
|
|
|
|
test_expect_success 'complain about index name' '
|
|
|
|
|
# Normal case { .pack, .idx, .rev }
|
|
|
|
|
cat test-1-${packname_1}.pack >test-complain-0.pack &&
|
|
|
|
|
git index-pack -o test-complain-0.idx --rev-index test-complain-0.pack &&
|
|
|
|
|
test -f test-complain-0.idx &&
|
|
|
|
|
test -f test-complain-0.rev &&
|
|
|
|
|
|
2023-08-25 18:06:28 +03:00
|
|
|
# Non .idx suffix -- implicitly omits the .rev
|
2023-08-25 16:58:27 +03:00
|
|
|
cat test-1-${packname_1}.pack >test-complain-1.pack &&
|
2023-08-25 18:06:28 +03:00
|
|
|
git index-pack -o test-complain-1.idx-suffix --rev-index test-complain-1.pack &&
|
|
|
|
|
test -f test-complain-1.idx-suffix &&
|
2023-08-25 16:58:27 +03:00
|
|
|
! test -f test-complain-1.rev
|
|
|
|
|
'
|
|
|
|
|
|
2008-03-05 10:46:51 +03:00
|
|
|
test_expect_success 'unpacking with --strict' '
|
2008-03-05 11:14:32 +03:00
|
|
|
|
|
|
|
|
for j in a b c d e f g
|
|
|
|
|
do
|
|
|
|
|
for i in 0 1 2 3 4 5 6 7 8 9
|
|
|
|
|
do
|
|
|
|
|
o=$(echo $j$i | git hash-object -w --stdin) &&
|
2021-12-09 08:11:14 +03:00
|
|
|
echo "100644 $o 0 $j$i" || return 1
|
2008-03-05 11:14:32 +03:00
|
|
|
done
|
|
|
|
|
done >LIST &&
|
|
|
|
|
rm -f .git/index &&
|
|
|
|
|
git update-index --index-info <LIST &&
|
|
|
|
|
LIST=$(git write-tree) &&
|
|
|
|
|
rm -f .git/index &&
|
|
|
|
|
head -n 10 LIST | git update-index --index-info &&
|
|
|
|
|
LI=$(git write-tree) &&
|
|
|
|
|
rm -f .git/index &&
|
|
|
|
|
tail -n 10 LIST | git update-index --index-info &&
|
|
|
|
|
ST=$(git write-tree) &&
|
2018-03-27 20:31:37 +03:00
|
|
|
git rev-list --objects "$LIST" "$LI" "$ST" >actual &&
|
|
|
|
|
PACK5=$( git pack-objects test-5 <actual ) &&
|
2021-12-09 08:11:05 +03:00
|
|
|
PACK6=$( test_write_lines "$LIST" "$LI" "$ST" | git pack-objects test-6 ) &&
|
2008-03-05 11:14:32 +03:00
|
|
|
test_create_repo test-5 &&
|
|
|
|
|
(
|
|
|
|
|
cd test-5 &&
|
|
|
|
|
git unpack-objects --strict <../test-5-$PACK5.pack &&
|
|
|
|
|
git ls-tree -r $LIST &&
|
|
|
|
|
git ls-tree -r $LI &&
|
|
|
|
|
git ls-tree -r $ST
|
|
|
|
|
) &&
|
|
|
|
|
test_create_repo test-6 &&
|
|
|
|
|
(
|
|
|
|
|
# tree-only into empty repo -- many unreachables
|
|
|
|
|
cd test-6 &&
|
|
|
|
|
test_must_fail git unpack-objects --strict <../test-6-$PACK6.pack
|
|
|
|
|
) &&
|
|
|
|
|
(
|
|
|
|
|
# already populated -- no unreachables
|
|
|
|
|
cd test-5 &&
|
|
|
|
|
git unpack-objects --strict <../test-6-$PACK6.pack
|
|
|
|
|
)
|
|
|
|
|
'
|
|
|
|
|
|
2008-03-07 10:39:53 +03:00
|
|
|
test_expect_success 'index-pack with --strict' '
|
|
|
|
|
|
|
|
|
|
for j in a b c d e f g
|
|
|
|
|
do
|
|
|
|
|
for i in 0 1 2 3 4 5 6 7 8 9
|
|
|
|
|
do
|
|
|
|
|
o=$(echo $j$i | git hash-object -w --stdin) &&
|
2021-12-09 08:11:14 +03:00
|
|
|
echo "100644 $o 0 $j$i" || return 1
|
2008-03-07 10:39:53 +03:00
|
|
|
done
|
|
|
|
|
done >LIST &&
|
|
|
|
|
rm -f .git/index &&
|
|
|
|
|
git update-index --index-info <LIST &&
|
|
|
|
|
LIST=$(git write-tree) &&
|
|
|
|
|
rm -f .git/index &&
|
|
|
|
|
head -n 10 LIST | git update-index --index-info &&
|
|
|
|
|
LI=$(git write-tree) &&
|
|
|
|
|
rm -f .git/index &&
|
|
|
|
|
tail -n 10 LIST | git update-index --index-info &&
|
|
|
|
|
ST=$(git write-tree) &&
|
2018-03-27 20:31:37 +03:00
|
|
|
git rev-list --objects "$LIST" "$LI" "$ST" >actual &&
|
|
|
|
|
PACK5=$( git pack-objects test-5 <actual ) &&
|
2021-12-09 08:11:05 +03:00
|
|
|
PACK6=$( test_write_lines "$LIST" "$LI" "$ST" | git pack-objects test-6 ) &&
|
2008-03-07 10:39:53 +03:00
|
|
|
test_create_repo test-7 &&
|
|
|
|
|
(
|
|
|
|
|
cd test-7 &&
|
|
|
|
|
git index-pack --strict --stdin <../test-5-$PACK5.pack &&
|
|
|
|
|
git ls-tree -r $LIST &&
|
|
|
|
|
git ls-tree -r $LI &&
|
|
|
|
|
git ls-tree -r $ST
|
|
|
|
|
) &&
|
|
|
|
|
test_create_repo test-8 &&
|
|
|
|
|
(
|
|
|
|
|
# tree-only into empty repo -- many unreachables
|
|
|
|
|
cd test-8 &&
|
|
|
|
|
test_must_fail git index-pack --strict --stdin <../test-6-$PACK6.pack
|
|
|
|
|
) &&
|
|
|
|
|
(
|
|
|
|
|
# already populated -- no unreachables
|
|
|
|
|
cd test-7 &&
|
|
|
|
|
git index-pack --strict --stdin <../test-6-$PACK6.pack
|
|
|
|
|
)
|
|
|
|
|
'
|
|
|
|
|
|
2024-02-01 04:38:02 +03:00
|
|
|
test_expect_success 'setup for --strict and --fsck-objects downgrading fsck msgs' '
|
2024-02-01 04:38:01 +03:00
|
|
|
git init strict &&
|
|
|
|
|
(
|
|
|
|
|
cd strict &&
|
|
|
|
|
test_commit first hello &&
|
|
|
|
|
cat >commit <<-EOF &&
|
|
|
|
|
tree $(git rev-parse HEAD^{tree})
|
|
|
|
|
parent $(git rev-parse HEAD)
|
|
|
|
|
author A U Thor
|
|
|
|
|
committer A U Thor
|
|
|
|
|
|
|
|
|
|
commit: this is a commit with bad emails
|
|
|
|
|
|
|
|
|
|
EOF
|
|
|
|
|
git hash-object --literally -t commit -w --stdin <commit >commit_list &&
|
2024-02-01 04:38:02 +03:00
|
|
|
git pack-objects test <commit_list >pack-name
|
2024-02-01 04:38:01 +03:00
|
|
|
)
|
|
|
|
|
'
|
|
|
|
|
|
2024-02-01 04:38:02 +03:00
|
|
|
test_with_bad_commit () {
|
|
|
|
|
must_fail_arg="$1" &&
|
|
|
|
|
must_pass_arg="$2" &&
|
|
|
|
|
(
|
|
|
|
|
cd strict &&
|
2024-03-15 07:57:26 +03:00
|
|
|
test_must_fail git index-pack "$must_fail_arg" "test-$(cat pack-name).pack" &&
|
2024-02-01 04:38:02 +03:00
|
|
|
git index-pack "$must_pass_arg" "test-$(cat pack-name).pack"
|
|
|
|
|
)
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
test_expect_success 'index-pack with --strict downgrading fsck msgs' '
|
|
|
|
|
test_with_bad_commit --strict --strict="missingEmail=ignore"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'index-pack with --fsck-objects downgrading fsck msgs' '
|
|
|
|
|
test_with_bad_commit --fsck-objects --fsck-objects="missingEmail=ignore"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'cleanup for --strict and --fsck-objects downgrading fsck msgs' '
|
|
|
|
|
rm -rf strict
|
|
|
|
|
'
|
|
|
|
|
|
2010-02-04 06:48:26 +03:00
|
|
|
test_expect_success 'honor pack.packSizeLimit' '
|
2010-02-04 06:48:28 +03:00
|
|
|
git config pack.packSizeLimit 3m &&
|
2010-02-04 06:48:26 +03:00
|
|
|
packname_10=$(git pack-objects test-10 <obj-list) &&
|
2010-02-04 06:48:28 +03:00
|
|
|
test 2 = $(ls test-10-*.pack | wc -l)
|
2010-02-04 06:48:26 +03:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'verify resulting packs' '
|
|
|
|
|
git verify-pack test-10-*.pack
|
|
|
|
|
'
|
|
|
|
|
|
2010-02-04 06:48:28 +03:00
|
|
|
test_expect_success 'tolerate packsizelimit smaller than biggest object' '
|
|
|
|
|
git config pack.packSizeLimit 1 &&
|
2010-02-04 06:48:26 +03:00
|
|
|
packname_11=$(git pack-objects test-11 <obj-list) &&
|
2010-02-08 18:39:01 +03:00
|
|
|
test 5 = $(ls test-11-*.pack | wc -l)
|
2008-11-12 21:23:58 +03:00
|
|
|
'
|
|
|
|
|
|
2010-02-04 06:48:26 +03:00
|
|
|
test_expect_success 'verify resulting packs' '
|
|
|
|
|
git verify-pack test-11-*.pack
|
|
|
|
|
'
|
|
|
|
|
|
2016-12-16 05:30:59 +03:00
|
|
|
test_expect_success 'set up pack for non-repo tests' '
|
|
|
|
|
# make sure we have a pack with no matching index file
|
|
|
|
|
cp test-1-*.pack foo.pack
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'index-pack --stdin complains of non-repo' '
|
2020-06-19 20:55:59 +03:00
|
|
|
nongit test_must_fail git index-pack --object-format=$(test_oid algo) --stdin <foo.pack &&
|
2016-12-16 05:30:59 +03:00
|
|
|
test_path_is_missing non-repo/.git
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'index-pack <pack> works in non-repo' '
|
2020-06-19 20:55:59 +03:00
|
|
|
nongit git index-pack --object-format=$(test_oid algo) ../foo.pack &&
|
2016-12-16 05:30:59 +03:00
|
|
|
test_path_is_file foo.idx
|
|
|
|
|
'
|
|
|
|
|
|
prepare_commit_graft: treat non-repository as a noop
The parse_commit_buffer() function consults lookup_commit_graft()
to see if we need to rewrite parents. The latter will look
at $GIT_DIR/info/grafts. If you're outside of a repository,
then this will trigger a BUG() as of b1ef400eec (setup_git_env:
avoid blind fall-back to ".git", 2016-10-20).
It's probably uncommon to actually parse a commit outside of
a repository, but you can see it in action with:
cd /not/a/git/repo
git index-pack --strict /some/file.pack
This works fine without --strict, but the fsck checks will
try to parse any commits, triggering the BUG(). We can fix
that by teaching the graft code to behave as if there are no
grafts when we aren't in a repository.
Arguably index-pack (and fsck) are wrong to consider grafts
at all. So another solution is to disable grafts entirely
for those commands. But given that the graft feature is
deprecated anyway, it's not worth even thinking through the
ramifications that might have.
There is one other corner case I considered here. What
should:
cd /not/a/git/repo
export GIT_GRAFT_FILE=/file/with/grafts
git index-pack --strict /some/file.pack
do? We don't have a repository, but the user has pointed us
directly at a graft file, which we could respect. I believe
this case did work that way prior to b1ef400eec. However,
fixing it now would be pretty invasive. Back then we would
just call into setup_git_env() even without a repository.
But these days it actually takes a git_dir argument. So
there would be a fair bit of refactoring of the setup code
involved.
Given the obscurity of this case, plus the fact that grafts
are deprecated and probably shouldn't work under index-pack
anyway, it's not worth pursuing further. This patch at least
un-breaks the common case where you're _not_ using grafts,
but we BUG() anyway trying to even find that out.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-06-01 01:42:53 +03:00
|
|
|
test_expect_success 'index-pack --strict <pack> works in non-repo' '
|
|
|
|
|
rm -f foo.idx &&
|
2020-06-19 20:55:59 +03:00
|
|
|
nongit git index-pack --strict --object-format=$(test_oid algo) ../foo.pack &&
|
prepare_commit_graft: treat non-repository as a noop
The parse_commit_buffer() function consults lookup_commit_graft()
to see if we need to rewrite parents. The latter will look
at $GIT_DIR/info/grafts. If you're outside of a repository,
then this will trigger a BUG() as of b1ef400eec (setup_git_env:
avoid blind fall-back to ".git", 2016-10-20).
It's probably uncommon to actually parse a commit outside of
a repository, but you can see it in action with:
cd /not/a/git/repo
git index-pack --strict /some/file.pack
This works fine without --strict, but the fsck checks will
try to parse any commits, triggering the BUG(). We can fix
that by teaching the graft code to behave as if there are no
grafts when we aren't in a repository.
Arguably index-pack (and fsck) are wrong to consider grafts
at all. So another solution is to disable grafts entirely
for those commands. But given that the graft feature is
deprecated anyway, it's not worth even thinking through the
ramifications that might have.
There is one other corner case I considered here. What
should:
cd /not/a/git/repo
export GIT_GRAFT_FILE=/file/with/grafts
git index-pack --strict /some/file.pack
do? We don't have a repository, but the user has pointed us
directly at a graft file, which we could respect. I believe
this case did work that way prior to b1ef400eec. However,
fixing it now would be pretty invasive. Back then we would
just call into setup_git_env() even without a repository.
But these days it actually takes a git_dir argument. So
there would be a fair bit of refactoring of the setup code
involved.
Given the obscurity of this case, plus the fact that grafts
are deprecated and probably shouldn't work under index-pack
anyway, it's not worth pursuing further. This patch at least
un-breaks the common case where you're _not_ using grafts,
but we BUG() anyway trying to even find that out.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-06-01 01:42:53 +03:00
|
|
|
test_path_is_file foo.idx
|
|
|
|
|
'
|
|
|
|
|
|
2021-03-18 01:47:03 +03:00
|
|
|
test_expect_success !PTHREADS,!FAIL_PREREQS \
|
|
|
|
|
'index-pack --threads=N or pack.threads=N warns when no pthreads' '
|
2017-05-25 22:45:32 +03:00
|
|
|
test_must_fail git index-pack --threads=2 2>err &&
|
|
|
|
|
grep ^warning: err >warnings &&
|
|
|
|
|
test_line_count = 1 warnings &&
|
|
|
|
|
grep -F "no threads support, ignoring --threads=2" err &&
|
|
|
|
|
|
|
|
|
|
test_must_fail git -c pack.threads=2 index-pack 2>err &&
|
|
|
|
|
grep ^warning: err >warnings &&
|
|
|
|
|
test_line_count = 1 warnings &&
|
|
|
|
|
grep -F "no threads support, ignoring pack.threads" err &&
|
|
|
|
|
|
|
|
|
|
test_must_fail git -c pack.threads=2 index-pack --threads=4 2>err &&
|
|
|
|
|
grep ^warning: err >warnings &&
|
|
|
|
|
test_line_count = 2 warnings &&
|
|
|
|
|
grep -F "no threads support, ignoring --threads=4" err &&
|
|
|
|
|
grep -F "no threads support, ignoring pack.threads" err
|
|
|
|
|
'
|
|
|
|
|
|
2021-03-18 01:47:03 +03:00
|
|
|
test_expect_success !PTHREADS,!FAIL_PREREQS \
|
|
|
|
|
'pack-objects --threads=N or pack.threads=N warns when no pthreads' '
|
2017-05-25 22:45:32 +03:00
|
|
|
git pack-objects --threads=2 --stdout --all </dev/null >/dev/null 2>err &&
|
|
|
|
|
grep ^warning: err >warnings &&
|
|
|
|
|
test_line_count = 1 warnings &&
|
|
|
|
|
grep -F "no threads support, ignoring --threads" err &&
|
|
|
|
|
|
|
|
|
|
git -c pack.threads=2 pack-objects --stdout --all </dev/null >/dev/null 2>err &&
|
|
|
|
|
grep ^warning: err >warnings &&
|
2017-05-25 22:45:33 +03:00
|
|
|
test_line_count = 1 warnings &&
|
2017-05-25 22:45:32 +03:00
|
|
|
grep -F "no threads support, ignoring pack.threads" err &&
|
|
|
|
|
|
|
|
|
|
git -c pack.threads=2 pack-objects --threads=4 --stdout --all </dev/null >/dev/null 2>err &&
|
|
|
|
|
grep ^warning: err >warnings &&
|
|
|
|
|
test_line_count = 2 warnings &&
|
|
|
|
|
grep -F "no threads support, ignoring --threads" err &&
|
|
|
|
|
grep -F "no threads support, ignoring pack.threads" err
|
|
|
|
|
'
|
|
|
|
|
|
2018-04-14 18:35:05 +03:00
|
|
|
test_expect_success 'pack-objects in too-many-packs mode' '
|
|
|
|
|
GIT_TEST_FULL_IN_PACK_ARRAY=1 git repack -ad &&
|
|
|
|
|
git fsck
|
|
|
|
|
'
|
|
|
|
|
|
2018-10-30 21:43:30 +03:00
|
|
|
test_expect_success 'setup: fake a SHA1 hash collision' '
|
|
|
|
|
git init corrupt &&
|
|
|
|
|
(
|
|
|
|
|
cd corrupt &&
|
|
|
|
|
long_a=$(git hash-object -w ../a | sed -e "s!^..!&/!") &&
|
|
|
|
|
long_b=$(git hash-object -w ../b | sed -e "s!^..!&/!") &&
|
|
|
|
|
test -f .git/objects/$long_b &&
|
|
|
|
|
cp -f .git/objects/$long_a \
|
|
|
|
|
.git/objects/$long_b
|
|
|
|
|
)
|
2018-10-30 21:43:29 +03:00
|
|
|
'
|
2010-02-04 06:48:26 +03:00
|
|
|
|
2018-10-30 21:43:29 +03:00
|
|
|
test_expect_success 'make sure index-pack detects the SHA1 collision' '
|
2018-10-30 21:43:30 +03:00
|
|
|
(
|
|
|
|
|
cd corrupt &&
|
|
|
|
|
test_must_fail git index-pack -o ../bad.idx ../test-3.pack 2>msg &&
|
2023-10-31 08:23:30 +03:00
|
|
|
test_grep "SHA1 COLLISION FOUND" msg
|
2018-10-30 21:43:30 +03:00
|
|
|
)
|
2018-10-30 21:43:29 +03:00
|
|
|
'
|
2010-02-04 06:48:26 +03:00
|
|
|
|
2018-10-30 21:43:29 +03:00
|
|
|
test_expect_success 'make sure index-pack detects the SHA1 collision (large blobs)' '
|
2018-10-30 21:43:30 +03:00
|
|
|
(
|
|
|
|
|
cd corrupt &&
|
|
|
|
|
test_must_fail git -c core.bigfilethreshold=1 index-pack -o ../bad.idx ../test-3.pack 2>msg &&
|
2023-10-31 08:23:30 +03:00
|
|
|
test_grep "SHA1 COLLISION FOUND" msg
|
2018-10-30 21:43:30 +03:00
|
|
|
)
|
2018-10-30 21:43:29 +03:00
|
|
|
'
|
2012-05-24 17:55:44 +04:00
|
|
|
|
2020-07-21 03:21:44 +03:00
|
|
|
test_expect_success 'prefetch objects' '
|
|
|
|
|
rm -rf server client &&
|
|
|
|
|
|
|
|
|
|
git init server &&
|
|
|
|
|
test_config -C server uploadpack.allowanysha1inwant 1 &&
|
|
|
|
|
test_config -C server uploadpack.allowfilter 1 &&
|
|
|
|
|
test_config -C server protocol.version 2 &&
|
|
|
|
|
|
|
|
|
|
echo one >server/one &&
|
|
|
|
|
git -C server add one &&
|
|
|
|
|
git -C server commit -m one &&
|
|
|
|
|
git -C server branch one_branch &&
|
|
|
|
|
|
|
|
|
|
echo two_a >server/two_a &&
|
|
|
|
|
echo two_b >server/two_b &&
|
|
|
|
|
git -C server add two_a two_b &&
|
|
|
|
|
git -C server commit -m two &&
|
|
|
|
|
|
|
|
|
|
echo three >server/three &&
|
|
|
|
|
git -C server add three &&
|
|
|
|
|
git -C server commit -m three &&
|
|
|
|
|
git -C server branch three_branch &&
|
|
|
|
|
|
|
|
|
|
# Clone, fetch "two" with blobs excluded, and re-push it. This requires
|
|
|
|
|
# the client to have the blobs of "two" - verify that these are
|
|
|
|
|
# prefetched in one batch.
|
|
|
|
|
git clone --filter=blob:none --single-branch -b one_branch \
|
|
|
|
|
"file://$(pwd)/server" client &&
|
|
|
|
|
test_config -C client protocol.version 2 &&
|
|
|
|
|
TWO=$(git -C server rev-parse three_branch^) &&
|
|
|
|
|
git -C client fetch --filter=blob:none origin "$TWO" &&
|
|
|
|
|
GIT_TRACE_PACKET=$(pwd)/trace git -C client push origin "$TWO":refs/heads/two_branch &&
|
2020-08-18 07:01:36 +03:00
|
|
|
grep "fetch> done" trace >donelines &&
|
2020-07-21 03:21:44 +03:00
|
|
|
test_line_count = 1 donelines
|
|
|
|
|
'
|
|
|
|
|
|
2021-05-01 17:03:37 +03:00
|
|
|
test_expect_success 'negative window clamps to 0' '
|
|
|
|
|
git pack-objects --progress --window=-1 neg-window <obj-list 2>stderr &&
|
|
|
|
|
check_deltas stderr = 0
|
|
|
|
|
'
|
|
|
|
|
|
2005-06-26 15:29:18 +04:00
|
|
|
test_done
|
