Hi,
Jeffrey Walton wrote:
> Fedora 29, x86_64. One failed self test:
>
> *** t0021-conversion.sh ***
[...]
> not ok 13 - disable filter with empty override
> #
> # test_config_global filter.disable.smudge false &&
> # test_config_global filter.disable.clean false &&
> # test_config filter.disable.smudge false &&
> # test_config filter.disable.clean false &&
> #
> # echo "*.disable filter=disable" >.gitattributes &&
> #
> # echo test >test.disable &&
> # git -c filter.disable.clean= add test.disable 2>err &&
> # test_must_be_empty err &&
> # rm -f test.disable &&
> # git -c filter.disable.smudge= checkout -- test.disable 2>err
> &&
> # test_must_be_empty err
> #
[...]
> # failed 1 among 26 test(s)
> 1..26
> gmake[2]: *** [Makefile:56: t0021-conversion.sh] Error 1
>
> Does anyone need a config.log or other test data?
It would probably help to know what commit you're building.
The verbose test output would also be useful, e.g.:
cd t && ./t0021-conversion.sh -v -i
If it's not reliably reproducible, the --stress* options
might help catch a failing run.
FWIW, I just built and ran the tests on a Fedora 29
container for master, next, and pu a few times (some with
various --stress options) without any test failures.
I did this with and without a config.mak from the fedora git
packages. I've never used the configure script, it seems
like unnecessary overhead.
$ git branch -v
master 6e0cc67761 Start 2.22 cycle
next 541d9dca55 Merge branch 'yb/utf-16le-bom-spellfix' into next
* pu 7eadd8ba98 Merge branch 'js/remote-curl-i18n' into pu
--
Todd
