Re: Git 2.25 and failed self tests on OS X

From: Jeff King <peff@peff.net>
Date: Feb 3, 2020, 08:43 UTC
Message-ID: <20200203084356.GB2164@coredump.intra.peff.net>
In-Reply-To: <CAH8yC8kXPi0teqdZ8NRJ677Z6btbmdafR=y4MFFaKZgZrB=d4A@mail.gmail.com>

On Sun, Feb 02, 2020 at 11:08:17PM -0500, Jeffrey Walton wrote:

Show 18 quoted lines

> 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\""

It's hard to see what's going on with this output. Try running:

  ./t3902-quoted.sh -v -x -i

to get more verbose output.

Looking at this test, it tries to create files with funny characters in the names. Presumably your filesystem isn't happy with one or more of them. The verbose output will probably make it clear which.

Version 10.9 isn't incredibly new, but these tests have been around a long time. If OS X has a problem with these filenames, it seems odd for it to be surfacing now.

Do you know what filesystem you're using? You aren't running the tests by any chance on a network mount from a Windows machine?

-Peff