Explain seemingly pointless use of system in difftool
[git/jnareb-git.git] / t / t6011-rev-list-with-bad-commit.sh
blobe51eb41f4b9575d2b51d8d4d255ff5ab7a0889ad
1 #!/bin/sh
3 test_description='git rev-list should notice bad commits'
5 . ./test-lib.sh
7 # Note:
8 # - compression level is set to zero to make "corruptions" easier to perform
9 # - reflog is disabled to avoid extra references which would twart the test
11 test_expect_success 'setup' \
13 git init &&
14 git config core.compression 0 &&
15 git config core.logallrefupdates false &&
16 echo "foo" > foo &&
17 git add foo &&
18 git commit -m "first commit" &&
19 echo "bar" > bar &&
20 git add bar &&
21 git commit -m "second commit" &&
22 echo "baz" > baz &&
23 git add baz &&
24 git commit -m "third commit" &&
25 echo "foo again" >> foo &&
26 git add foo &&
27 git commit -m "fourth commit" &&
28 git repack -a -f -d
31 test_expect_success 'verify number of revisions' \
33 revs=$(git rev-list --all | wc -l) &&
34 test $revs -eq 4 &&
35 first_commit=$(git rev-parse HEAD~3)
38 test_expect_success 'corrupt second commit object' \
40 perl -i.bak -pe "s/second commit/socond commit/" .git/objects/pack/*.pack &&
41 test_must_fail git fsck --full
44 test_expect_success 'rev-list should fail' \
46 test_must_fail git rev-list --all > /dev/null
49 test_expect_success 'git repack _MUST_ fail' \
51 test_must_fail git repack -a -f -d
54 test_expect_success 'first commit is still available' \
56 git log $first_commit
59 test_done