]> git.ipfire.org Git - thirdparty/git.git/commitdiff
t1092: revert the "-1" hack for emulating "no progress meter"
authorJunio C Hamano <gitster@pobox.com>
Tue, 25 May 2021 20:52:34 +0000 (05:52 +0900)
committerJunio C Hamano <gitster@pobox.com>
Tue, 25 May 2021 21:23:58 +0000 (06:23 +0900)
This looked like a good idea, but it seems to break tests on 32-bit
builds rather badly.  Revert to just use "100 thousands must be big
enough" for now.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t1092-sparse-checkout-compatibility.sh

index 58ac9377e4f0c1901eb757ebd4f59bf77281cf7f..e9a815ca7aaaa84099b721af7db520c9f1de594b 100755 (executable)
@@ -106,18 +106,18 @@ init_repos () {
 run_on_sparse () {
        (
                cd sparse-checkout &&
-               GIT_PROGRESS_DELAY=-1 "$@" >../sparse-checkout-out 2>../sparse-checkout-err
+               GIT_PROGRESS_DELAY=100000 "$@" >../sparse-checkout-out 2>../sparse-checkout-err
        ) &&
        (
                cd sparse-index &&
-               GIT_PROGRESS_DELAY=-1 "$@" >../sparse-index-out 2>../sparse-index-err
+               GIT_PROGRESS_DELAY=100000 "$@" >../sparse-index-out 2>../sparse-index-err
        )
 }
 
 run_on_all () {
        (
                cd full-checkout &&
-               GIT_PROGRESS_DELAY=-1 "$@" >../full-checkout-out 2>../full-checkout-err
+               GIT_PROGRESS_DELAY=100000 "$@" >../full-checkout-out 2>../full-checkout-err
        ) &&
        run_on_sparse "$@"
 }