Re: Tests failed with GIT_TEST_FAIL_PREREQS and/or GIT_TEST_PROTOCOL_VERSION

[Taylor Blau <me@ttaylorr.com>]

Hi,

On Tue, Mar 16, 2021 at 10:45:20AM +0100, Son Luong Ngoc wrote:
> Hi folks,
>
> Running the test suit with GIT_TEST_FAIL_PREREQS=1 on master (and
> next) seem to result in some failures:

Ack, thanks for reporting.

> A quick git-bisect run seems to point back to this commit:
>
> 3b1ca60f8f317b483c8c1805ab500ff2b014cbec is the first bad commit
> commit 3b1ca60f8f317b483c8c1805ab500ff2b014cbec
> Author: Taylor Blau <me@ttaylorr.com>
> Date:   Tue Dec 8 17:03:14 2020 -0500

Hmm. I get a different result.

    $ cat run.sh
    #!/bin/sh
    make -j20 DEVELOPER=1 O=0 && cd t && GIT_TEST_FAIL_PREREQS=1 ./t5300-*.sh -i
    $ git bisect start
    $ git bisect bad
    $ git bisect good v2.30.0
    Bisecting: 453 revisions left to test after this (roughly 9 steps)
    $ git bisect run $PWD/run.sh
    [snip]
    a926c4b904bdc339568c2898af955cdc61b31542 is the first bad commit
    commit a926c4b904bdc339568c2898af955cdc61b31542
    Author: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
    Date:   Thu Feb 11 02:53:51 2021 +0100

        tests: remove most uses of C_LOCALE_OUTPUT

>     ewah/ewah_bitmap.c: avoid open-coding ALLOC_GROW()

I'll take a look at what's going on here, but Ævar (cc'd) will probably
beat me to it.

Is it possible that your bisection script doesn't report success
properly? Bisecting the same range (v2.30.0..v2.31.0) with

    $ cat run.sh
    #!/bin/sh
    false

does say that my 3b1ca60f8f (ewah/ewah_bitmap.c: avoid open-coding
ALLOC_GROW(), 2020-12-08) is the first bad commit.

Thanks,
Taylor