Git 2.25 and failed self tests on OS X

Hi Everyone,

I'm seeing some self-tests failures building the 2.25 release tarball on OS X. I'm seeing it on the old PowerMac with OS X 10.5, and a modern Intel Mac with OS X 10.9. PowerMac failures are not too surprising, but the modern Mac should probably pass its self tests.

*** t3902-quoted.sh *** not ok 1 - setup # # # mkdir "$FN" && # for_each_name "echo initial >\"\$name\"" && # git add . && # git commit -q -m Initial && # # for_each_name "echo second >\"\$name\"" && # git commit -a -m Second && # # for_each_name "echo modified >\"\$name\"" # # ok 2 - setup expected files not ok 3 - check fully quoted output from ls-files # # # git ls-files >current && test_cmp expect.quoted current # # not ok 4 - check fully quoted output from diff-files # # # git diff --name-only >current && # test_cmp expect.quoted current # # not ok 5 - check fully quoted output from diff-index # # # git diff --name-only HEAD >current && # test_cmp expect.quoted current # # not ok 6 - check fully quoted output from diff-tree # # # git diff --name-only HEAD^ HEAD >current && # test_cmp expect.quoted current # # not ok 7 - check fully quoted output from ls-tree # # # git ls-tree --name-only -r HEAD >current && # test_cmp expect.quoted current # # ok 8 - setting core.quotepath not ok 9 - check fully quoted output from ls-files # # # git ls-files >current && test_cmp expect.raw current # # not ok 10 - check fully quoted output from diff-files # # # git diff --name-only >current && # test_cmp expect.raw current # # not ok 11 - check fully quoted output from diff-index # # # git diff --name-only HEAD >current && # test_cmp expect.raw current # # not ok 12 - check fully quoted output from diff-tree # # # git diff --name-only HEAD^ HEAD >current && # test_cmp expect.raw current # # not ok 13 - check fully quoted output from ls-tree # # # git ls-tree --name-only -r HEAD >current && # test_cmp expect.raw current # # # failed 11 among 13 test(s) 1..13

Setting LC_ALL=en_US.UTF-8 and LANG=en_US.UTF-8 did not help. (I've seen sed and awk produce unusual results when they are not set).

Jeff