Thanks, Ryenus, for reporting this problem.

Update in V3:

Based on our discussion, I've added the suggested GIT_PROGRESS_DELAY
environment variable. This allowed the existing tests to stick around with
one exception in the GC tests. The test remains, but we can no longer look
at the commit-graph output.

Update in V4:

The GIT_PROGRESS_DELAY check is extracted to a helper method so it can be
used with start_delayed_sparse_progress().

Derrick Stolee (2):
  progress: create GIT_PROGRESS_DELAY
  commit-graph: use start_delayed_progress()

 Documentation/git.txt   |  4 ++++
 commit-graph.c          |  2 +-
 progress.c              | 15 +++++++++++++--
 t/t5318-commit-graph.sh |  4 ++--
 t/t6500-gc.sh           |  6 ++----
 5 files changed, 22 insertions(+), 9 deletions(-)

base-commit: da72936f544fec5a335e66432610e4cef4430991

Submitted-As: https://public-inbox.org/git/pull.450.v4.git.1574351516.gitgitgadget@gmail.com
In-Reply-To: https://public-inbox.org/git/pull.450.git.1572969955.gitgitgadget@gmail.com
In-Reply-To: https://public-inbox.org/git/pull.450.v2.git.1572984842.gitgitgadget@gmail.com
In-Reply-To: https://public-inbox.org/git/pull.450.v3.git.1573148818.gitgitgadget@gmail.com