summaryrefslogtreecommitdiff
path: root/t/t6500-gc.sh
diff options
context:
space:
mode:
authorDerrick Stolee <dstolee@microsoft.com>2019-11-25 21:28:23 (GMT)
committerJunio C Hamano <gitster@pobox.com>2019-11-27 01:57:10 (GMT)
commitecc0869080701b5e252f74ed7b3d0156a5ec6112 (patch)
treeab0c7d597eea5b39421bda9ad6176d439540438d /t/t6500-gc.sh
parent44a4693bfcec1876b29cdaec3625819d80ea1280 (diff)
downloadgit-ecc0869080701b5e252f74ed7b3d0156a5ec6112.zip
git-ecc0869080701b5e252f74ed7b3d0156a5ec6112.tar.gz
git-ecc0869080701b5e252f74ed7b3d0156a5ec6112.tar.bz2
commit-graph: use start_delayed_progress()
When writing a commit-graph, we show progress along several commit walks. When we use start_delayed_progress(), the progress line will only appear if that step takes a decent amount of time. However, one place was missed: computing generation numbers. This is normally a very fast operation as all commits have been parsed in a previous step. But, this is showing up for all users no matter how few commits are being added. The tests that check for the progress output have already been updated to use GIT_PROGRESS_DELAY=0 to force the expected output. Helped-by: Jeff King <peff@peff.net> Reported-by: ryenus <ryenus@gmail.com> Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t6500-gc.sh')
-rwxr-xr-xt/t6500-gc.sh3
1 files changed, 2 insertions, 1 deletions
diff --git a/t/t6500-gc.sh b/t/t6500-gc.sh
index 7f79eed..0a69a67 100755
--- a/t/t6500-gc.sh
+++ b/t/t6500-gc.sh
@@ -109,7 +109,8 @@ test_expect_success 'gc --no-quiet' '
'
test_expect_success TTY 'with TTY: gc --no-quiet' '
- test_terminal git -c gc.writeCommitGraph=true gc --no-quiet >stdout 2>stderr &&
+ test_terminal env GIT_PROGRESS_DELAY=0 \
+ git -c gc.writeCommitGraph=true gc --no-quiet >stdout 2>stderr &&
test_must_be_empty stdout &&
test_i18ngrep "Enumerating objects" stderr &&
test_i18ngrep "Computing commit graph generation numbers" stderr