pr-960/derrickstolee/sparse-index/progress-fix-v1
tagged this
24 May 19:55
From: Derrick Stolee <dstolee@microsoft.com> The t1092-sparse-checkout-compatibility.sh tests compare the stdout and stderr for several Git commands across both full checkouts, sparse checkouts with a full index, and sparse checkouts with a sparse index. Since these are direct comparisons, sometimes a progress indicator can flush at unpredictable points, especially on slower machines. This causes the tests to be flaky. One standard way to avoid this is to add GIT_PROGRESS_DELAY=0 to the Git commands that are run, as this will force every progress indicator created with start_progress_delay() to be created immediately. However, there are some progress indicators that are created in the case of a full index that are not created with a sparse index. Moreover, their values may be different as those indexes have a different number of entries. Instead, use GIT_PROGRESS_DELAY=100000 to ensure that any reasonable machine running these tests would never display delayed progress indicators. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Submitted-As: https://lore.kernel.org/git/pull.960.git.1621886108515.gitgitgadget@gmail.com
Assets 2
-
2021-05-24T19:55:08Z -
2021-05-24T19:55:08Z -