Re: [PATCH] t1092: use GIT_PROGRESS_DELAY for consistent results
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 25, 2021, 21:14 UTC
- Message-ID
- <xmqqwnrmcy7l.fsf@gitster.g>
- In-Reply-To
- <xmqq1r9uee3r.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
Show 8 quoted lines
> Well, not so well X-<. It seems that some builds are not happy with > this change. See https://github.com/git/git/actions/runs/876229761 > specifically these two: > > https://github.com/git/git/runs/2669177395?check_suite_focus=true#step:7:3549 > https://github.com/git/git/runs/2669080101?check_suite_focus=true#step:6:988 > > I suspect that it has something to do with 32-bit platforms?
Reverting the change that was squashed in seems to do the job. https://github.com/git/git/actions/runs/876338380 is labelled as 'seen' but it is 'next' that failed in the message I am responding to plus the revert of s/=100000/=-1/g.
Let's queue the 100000 version for now and get the =inf patch applied after the release.
Thanks.