t / t6500-gc.shon commit clean: show an error message when the path is too long (b09364c)
   1#!/bin/sh
   2
   3test_description='basic git gc tests
   4'
   5
   6. ./test-lib.sh
   7. "$TEST_DIRECTORY"/lib-terminal.sh
   8
   9test_expect_success 'setup' '
  10        # do not let the amount of physical memory affects gc
  11        # behavior, make sure we always pack everything to one pack by
  12        # default
  13        git config gc.bigPackThreshold 2g
  14'
  15
  16test_expect_success 'gc empty repository' '
  17        git gc
  18'
  19
  20test_expect_success 'gc does not leave behind pid file' '
  21        git gc &&
  22        test_path_is_missing .git/gc.pid
  23'
  24
  25test_expect_success 'gc --gobbledegook' '
  26        test_expect_code 129 git gc --nonsense 2>err &&
  27        test_i18ngrep "[Uu]sage: git gc" err
  28'
  29
  30test_expect_success 'gc -h with invalid configuration' '
  31        mkdir broken &&
  32        (
  33                cd broken &&
  34                git init &&
  35                echo "[gc] pruneexpire = CORRUPT" >>.git/config &&
  36                test_expect_code 129 git gc -h >usage 2>&1
  37        ) &&
  38        test_i18ngrep "[Uu]sage" broken/usage
  39'
  40
  41test_expect_success 'gc is not aborted due to a stale symref' '
  42        git init remote &&
  43        (
  44                cd remote &&
  45                test_commit initial &&
  46                git clone . ../client &&
  47                git branch -m develop &&
  48                cd ../client &&
  49                git fetch --prune &&
  50                git gc
  51        )
  52'
  53
  54test_expect_success 'gc --keep-largest-pack' '
  55        test_create_repo keep-pack &&
  56        (
  57                cd keep-pack &&
  58                test_commit one &&
  59                test_commit two &&
  60                test_commit three &&
  61                git gc &&
  62                ( cd .git/objects/pack && ls *.pack ) >pack-list &&
  63                test_line_count = 1 pack-list &&
  64                BASE_PACK=.git/objects/pack/pack-*.pack &&
  65                test_commit four &&
  66                git repack -d &&
  67                test_commit five &&
  68                git repack -d &&
  69                ( cd .git/objects/pack && ls *.pack ) >pack-list &&
  70                test_line_count = 3 pack-list &&
  71                git gc --keep-largest-pack &&
  72                ( cd .git/objects/pack && ls *.pack ) >pack-list &&
  73                test_line_count = 2 pack-list &&
  74                test_path_is_file $BASE_PACK &&
  75                git fsck
  76        )
  77'
  78
  79test_expect_success 'auto gc with too many loose objects does not attempt to create bitmaps' '
  80        test_config gc.auto 3 &&
  81        test_config gc.autodetach false &&
  82        test_config pack.writebitmaps true &&
  83        # We need to create two object whose sha1s start with 17
  84        # since this is what git gc counts.  As it happens, these
  85        # two blobs will do so.
  86        test_commit 263 &&
  87        test_commit 410 &&
  88        # Our first gc will create a pack; our second will create a second pack
  89        git gc --auto &&
  90        ls .git/objects/pack | sort >existing_packs &&
  91        test_commit 523 &&
  92        test_commit 790 &&
  93
  94        git gc --auto 2>err &&
  95        test_i18ngrep ! "^warning:" err &&
  96        ls .git/objects/pack/ | sort >post_packs &&
  97        comm -1 -3 existing_packs post_packs >new &&
  98        comm -2 -3 existing_packs post_packs >del &&
  99        test_line_count = 0 del && # No packs are deleted
 100        test_line_count = 2 new # There is one new pack and its .idx
 101'
 102
 103test_expect_success 'gc --no-quiet' '
 104        git -c gc.writeCommitGraph=true gc --no-quiet >stdout 2>stderr &&
 105        test_must_be_empty stdout &&
 106        test_line_count = 1 stderr &&
 107        test_i18ngrep "Computing commit graph generation numbers" stderr
 108'
 109
 110test_expect_success TTY 'with TTY: gc --no-quiet' '
 111        test_terminal git -c gc.writeCommitGraph=true gc --no-quiet >stdout 2>stderr &&
 112        test_must_be_empty stdout &&
 113        test_i18ngrep "Enumerating objects" stderr &&
 114        test_i18ngrep "Computing commit graph generation numbers" stderr
 115'
 116
 117test_expect_success 'gc --quiet' '
 118        git -c gc.writeCommitGraph=true gc --quiet >stdout 2>stderr &&
 119        test_must_be_empty stdout &&
 120        test_must_be_empty stderr
 121'
 122
 123test_expect_success 'gc.reflogExpire{Unreachable,}=never skips "expire" via "gc"' '
 124        test_config gc.reflogExpire never &&
 125        test_config gc.reflogExpireUnreachable never &&
 126
 127        GIT_TRACE=$(pwd)/trace.out git gc &&
 128
 129        # Check that git-pack-refs is run as a sanity check (done via
 130        # gc_before_repack()) but that git-expire is not.
 131        grep -E "^trace: (built-in|exec|run_command): git pack-refs --" trace.out &&
 132        ! grep -E "^trace: (built-in|exec|run_command): git reflog expire --" trace.out
 133'
 134
 135test_expect_success 'one of gc.reflogExpire{Unreachable,}=never does not skip "expire" via "gc"' '
 136        >trace.out &&
 137        test_config gc.reflogExpire never &&
 138        GIT_TRACE=$(pwd)/trace.out git gc &&
 139        grep -E "^trace: (built-in|exec|run_command): git reflog expire --" trace.out
 140'
 141
 142run_and_wait_for_auto_gc () {
 143        # We read stdout from gc for the side effect of waiting until the
 144        # background gc process exits, closing its fd 9.  Furthermore, the
 145        # variable assignment from a command substitution preserves the
 146        # exit status of the main gc process.
 147        # Note: this fd trickery doesn't work on Windows, but there is no
 148        # need to, because on Win the auto gc always runs in the foreground.
 149        doesnt_matter=$(git gc --auto 9>&1)
 150}
 151
 152test_expect_success 'background auto gc does not run if gc.log is present and recent but does if it is old' '
 153        test_commit foo &&
 154        test_commit bar &&
 155        git repack &&
 156        test_config gc.autopacklimit 1 &&
 157        test_config gc.autodetach true &&
 158        echo fleem >.git/gc.log &&
 159        git gc --auto 2>err &&
 160        test_i18ngrep "^warning:" err &&
 161        test_config gc.logexpiry 5.days &&
 162        test-tool chmtime =-345600 .git/gc.log &&
 163        git gc --auto &&
 164        test_config gc.logexpiry 2.days &&
 165        run_and_wait_for_auto_gc &&
 166        ls .git/objects/pack/pack-*.pack >packs &&
 167        test_line_count = 1 packs
 168'
 169
 170test_expect_success 'background auto gc respects lock for all operations' '
 171        # make sure we run a background auto-gc
 172        test_commit make-pack &&
 173        git repack &&
 174        test_config gc.autopacklimit 1 &&
 175        test_config gc.autodetach true &&
 176
 177        # create a ref whose loose presence we can use to detect a pack-refs run
 178        git update-ref refs/heads/should-be-loose HEAD &&
 179        test_path_is_file .git/refs/heads/should-be-loose &&
 180
 181        # now fake a concurrent gc that holds the lock; we can use our
 182        # shell pid so that it looks valid.
 183        hostname=$(hostname || echo unknown) &&
 184        shell_pid=$$ &&
 185        if test_have_prereq MINGW && test -f /proc/$shell_pid/winpid
 186        then
 187                # In Git for Windows, Bash (actually, the MSYS2 runtime) has a
 188                # different idea of PIDs than git.exe (actually Windows). Use
 189                # the Windows PID in this case.
 190                shell_pid=$(cat /proc/$shell_pid/winpid)
 191        fi &&
 192        printf "%d %s" "$shell_pid" "$hostname" >.git/gc.pid &&
 193
 194        # our gc should exit zero without doing anything
 195        run_and_wait_for_auto_gc &&
 196        test_path_is_file .git/refs/heads/should-be-loose
 197'
 198
 199# DO NOT leave a detached auto gc process running near the end of the
 200# test script: it can run long enough in the background to racily
 201# interfere with the cleanup in 'test_done'.
 202
 203test_done