t / t6500-gc.shon commit fixes from 'master' for 2.13.4 (2187e11)
   1#!/bin/sh
   2
   3test_description='basic git gc tests
   4'
   5
   6. ./test-lib.sh
   7
   8test_expect_success 'gc empty repository' '
   9        git gc
  10'
  11
  12test_expect_success 'gc does not leave behind pid file' '
  13        git gc &&
  14        test_path_is_missing .git/gc.pid
  15'
  16
  17test_expect_success 'gc --gobbledegook' '
  18        test_expect_code 129 git gc --nonsense 2>err &&
  19        test_i18ngrep "[Uu]sage: git gc" err
  20'
  21
  22test_expect_success 'gc -h with invalid configuration' '
  23        mkdir broken &&
  24        (
  25                cd broken &&
  26                git init &&
  27                echo "[gc] pruneexpire = CORRUPT" >>.git/config &&
  28                test_expect_code 129 git gc -h >usage 2>&1
  29        ) &&
  30        test_i18ngrep "[Uu]sage" broken/usage
  31'
  32
  33test_expect_success 'gc is not aborted due to a stale symref' '
  34        git init remote &&
  35        (
  36                cd remote &&
  37                test_commit initial &&
  38                git clone . ../client &&
  39                git branch -m develop &&
  40                cd ../client &&
  41                git fetch --prune &&
  42                git gc
  43        )
  44'
  45
  46test_expect_success 'auto gc with too many loose objects does not attempt to create bitmaps' '
  47        test_config gc.auto 3 &&
  48        test_config gc.autodetach false &&
  49        test_config pack.writebitmaps true &&
  50        # We need to create two object whose sha1s start with 17
  51        # since this is what git gc counts.  As it happens, these
  52        # two blobs will do so.
  53        test_commit 263 &&
  54        test_commit 410 &&
  55        # Our first gc will create a pack; our second will create a second pack
  56        git gc --auto &&
  57        ls .git/objects/pack | sort >existing_packs &&
  58        test_commit 523 &&
  59        test_commit 790 &&
  60
  61        git gc --auto 2>err &&
  62        test_i18ngrep ! "^warning:" err &&
  63        ls .git/objects/pack/ | sort >post_packs &&
  64        comm -1 -3 existing_packs post_packs >new &&
  65        comm -2 -3 existing_packs post_packs >del &&
  66        test_line_count = 0 del && # No packs are deleted
  67        test_line_count = 2 new # There is one new pack and its .idx
  68'
  69
  70run_and_wait_for_auto_gc () {
  71        # We read stdout from gc for the side effect of waiting until the
  72        # background gc process exits, closing its fd 9.  Furthermore, the
  73        # variable assignment from a command substitution preserves the
  74        # exit status of the main gc process.
  75        # Note: this fd trickery doesn't work on Windows, but there is no
  76        # need to, because on Win the auto gc always runs in the foreground.
  77        doesnt_matter=$(git gc --auto 9>&1)
  78}
  79
  80test_expect_success 'background auto gc does not run if gc.log is present and recent but does if it is old' '
  81        test_commit foo &&
  82        test_commit bar &&
  83        git repack &&
  84        test_config gc.autopacklimit 1 &&
  85        test_config gc.autodetach true &&
  86        echo fleem >.git/gc.log &&
  87        test_must_fail git gc --auto 2>err &&
  88        test_i18ngrep "^error:" err &&
  89        test_config gc.logexpiry 5.days &&
  90        test-chmtime =-345600 .git/gc.log &&
  91        test_must_fail git gc --auto &&
  92        test_config gc.logexpiry 2.days &&
  93        run_and_wait_for_auto_gc &&
  94        ls .git/objects/pack/pack-*.pack >packs &&
  95        test_line_count = 1 packs
  96'
  97
  98# DO NOT leave a detached auto gc process running near the end of the
  99# test script: it can run long enough in the background to racily
 100# interfere with the cleanup in 'test_done'.
 101
 102test_done