{"thread":{"id":"52741","subject":"Git 2.25 and failed self tests on OS X","startedAt":"2020-02-03T04:08:31Z","lastAt":"2020-02-03T16:53:30Z","messageCount":5,"participants":["Jeffrey Walton","Jeff King","Torsten Bögershausen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"391020","messageId":"CAH8yC8kXPi0teqdZ8NRJ677Z6btbmdafR=y4MFFaKZgZrB=d4A@mail.gmail.com","threadId":"52741","inReplyTo":null,"subject":"Git 2.25 and failed self tests on OS X","fromName":"Jeffrey Walton","fromEmail":"noloader@gmail.com","sentAt":"2020-02-03T04:08:17Z","receivedAt":"2020-02-03T04:08:31Z","isPatch":false,"sender":{"key":"noloader@gmail.com","avatar":null},"body":"Hi Everyone,\n\nI'm seeing some self-tests failures building the 2.25 release tarball\non OS X. I'm seeing it on the old PowerMac with OS X 10.5, and a\nmodern Intel Mac with OS X 10.9. PowerMac failures are not too\nsurprising, but the modern Mac should probably pass its self tests.\n\n*** t3902-quoted.sh ***\nnot ok 1 - setup\n#\n#\n#               mkdir \"$FN\" &&\n#               for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n#               git add . &&\n#               git commit -q -m Initial &&\n#\n#               for_each_name \"echo second >\\\"\\$name\\\"\" &&\n#               git commit -a -m Second &&\n#\n#               for_each_name \"echo modified >\\\"\\$name\\\"\"\n#\n#\nok 2 - setup expected files\nnot ok 3 - check fully quoted output from ls-files\n#\n#\n#               git ls-files >current && test_cmp expect.quoted current\n#\n#\nnot ok 4 - check fully quoted output from diff-files\n#\n#\n#               git diff --name-only >current &&\n#               test_cmp expect.quoted current\n#\n#\nnot ok 5 - check fully quoted output from diff-index\n#\n#\n#               git diff --name-only HEAD >current &&\n#               test_cmp expect.quoted current\n#\n#\nnot ok 6 - check fully quoted output from diff-tree\n#\n#\n#               git diff --name-only HEAD^ HEAD >current &&\n#               test_cmp expect.quoted current\n#\n#\nnot ok 7 - check fully quoted output from ls-tree\n#\n#\n#               git ls-tree --name-only -r HEAD >current &&\n#               test_cmp expect.quoted current\n#\n#\nok 8 - setting core.quotepath\nnot ok 9 - check fully quoted output from ls-files\n#\n#\n#               git ls-files >current && test_cmp expect.raw current\n#\n#\nnot ok 10 - check fully quoted output from diff-files\n#\n#\n#               git diff --name-only >current &&\n#               test_cmp expect.raw current\n#\n#\nnot ok 11 - check fully quoted output from diff-index\n#\n#\n#               git diff --name-only HEAD >current &&\n#               test_cmp expect.raw current\n#\n#\nnot ok 12 - check fully quoted output from diff-tree\n#\n#\n#               git diff --name-only HEAD^ HEAD >current &&\n#               test_cmp expect.raw current\n#\n#\nnot ok 13 - check fully quoted output from ls-tree\n#\n#\n#               git ls-tree --name-only -r HEAD >current &&\n#               test_cmp expect.raw current\n#\n#\n# failed 11 among 13 test(s)\n1..13\n\nSetting LC_ALL=en_US.UTF-8 and LANG=en_US.UTF-8 did not help. (I've\nseen sed and awk produce unusual results when they are not set).\n\nJeff\n"},{"id":"391027","messageId":"20200203084356.GB2164@coredump.intra.peff.net","threadId":"52741","inReplyTo":"CAH8yC8kXPi0teqdZ8NRJ677Z6btbmdafR=y4MFFaKZgZrB=d4A@mail.gmail.com","subject":"Re: Git 2.25 and failed self tests on OS X","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2020-02-03T08:43:56Z","receivedAt":"2020-02-03T08:43:58Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Feb 02, 2020 at 11:08:17PM -0500, Jeffrey Walton wrote:\n\n> I'm seeing some self-tests failures building the 2.25 release tarball\n> on OS X. I'm seeing it on the old PowerMac with OS X 10.5, and a\n> modern Intel Mac with OS X 10.9. PowerMac failures are not too\n> surprising, but the modern Mac should probably pass its self tests.\n> \n> *** t3902-quoted.sh ***\n> not ok 1 - setup\n> #\n> #\n> #               mkdir \"$FN\" &&\n> #               for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n> #               git add . &&\n> #               git commit -q -m Initial &&\n> #\n> #               for_each_name \"echo second >\\\"\\$name\\\"\" &&\n> #               git commit -a -m Second &&\n> #\n> #               for_each_name \"echo modified >\\\"\\$name\\\"\"\n\nIt's hard to see what's going on with this output. Try running:\n\n  ./t3902-quoted.sh -v -x -i\n\nto get more verbose output.\n\nLooking at this test, it tries to create files with funny characters in\nthe names. Presumably your filesystem isn't happy with one or more of\nthem. The verbose output will probably make it clear which.\n\nVersion 10.9 isn't incredibly new, but these tests have been around a\nlong time. If OS X has a problem with these filenames, it seems odd for\nit to be surfacing now.\n\nDo you know what filesystem you're using? You aren't running the tests\nby any chance on a network mount from a Windows machine?\n\n-Peff\n"},{"id":"391034","messageId":"CAH8yC8=-ht7D3CyM-YoJSfW3hueaWVp5WQz2+BJOFMjmt8aDsg@mail.gmail.com","threadId":"52741","inReplyTo":"20200203084356.GB2164@coredump.intra.peff.net","subject":"Re: Git 2.25 and failed self tests on OS X","fromName":"Jeffrey Walton","fromEmail":"noloader@gmail.com","sentAt":"2020-02-03T11:00:18Z","receivedAt":"2020-02-03T11:01:38Z","isPatch":false,"sender":{"key":"noloader@gmail.com","avatar":null},"body":"On Mon, Feb 3, 2020 at 3:43 AM Jeff King <peff@peff.net> wrote:\n>\n> On Sun, Feb 02, 2020 at 11:08:17PM -0500, Jeffrey Walton wrote:\n>\n> > I'm seeing some self-tests failures building the 2.25 release tarball\n> > on OS X. I'm seeing it on the old PowerMac with OS X 10.5, and a\n> > modern Intel Mac with OS X 10.9. PowerMac failures are not too\n> > surprising, but the modern Mac should probably pass its self tests.\n> >\n> > *** t3902-quoted.sh ***\n> > not ok 1 - setup\n> > #\n> > #\n> > #               mkdir \"$FN\" &&\n> > #               for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n> > #               git add . &&\n> > #               git commit -q -m Initial &&\n> > #\n> > #               for_each_name \"echo second >\\\"\\$name\\\"\" &&\n> > #               git commit -a -m Second &&\n> > #\n> > #               for_each_name \"echo modified >\\\"\\$name\\\"\"\n>\n> It's hard to see what's going on with this output. Try running:\n>\n>   ./t3902-quoted.sh -v -x -i\n>\n> to get more verbose output.\n>\n> Looking at this test, it tries to create files with funny characters in\n> the names. Presumably your filesystem isn't happy with one or more of\n> them. The verbose output will probably make it clear which.\n>\n> Version 10.9 isn't incredibly new, but these tests have been around a\n> long time. If OS X has a problem with these filenames, it seems odd for\n> it to be surfacing now.\n>\n> Do you know what filesystem you're using? You aren't running the tests\n> by any chance on a network mount from a Windows machine?\n\nAccording to `diskutil info /`, the filesystem is Journaled HFS+. The\ntests are running locally on the Mac after logging in over SSH.\n\nI'm wondering if Perl is the problem. I had to cut-over to OpenSSL 1.1\ndue to deprecation of 1.0.2. OpenSSL 1.1 increased Perl requirements,\nso now I have to build Perl, too. Previously I was not building Perl.\n\nI'm installing Perl 5.30.1, but it is a minimal install. I only\ninstall Text::Template Test::More (plus whatever else Perl installs on\nits own from cspan). However I could not install HTTP::Daemon\nHTTP::Request. There's some bug in the cspan installer. It gets stuck\non one package and tries to download/install it over and over again.\n\nDo you know if Git is using one of Perl's Text:: packages for the test?\n\nJeff\n"},{"id":"391036","messageId":"20200203110616.GB4153124@coredump.intra.peff.net","threadId":"52741","inReplyTo":"CAH8yC8=-ht7D3CyM-YoJSfW3hueaWVp5WQz2+BJOFMjmt8aDsg@mail.gmail.com","subject":"Re: Git 2.25 and failed self tests on OS X","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2020-02-03T11:06:16Z","receivedAt":"2020-02-03T11:06:18Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Feb 03, 2020 at 06:00:18AM -0500, Jeffrey Walton wrote:\n\n> I'm wondering if Perl is the problem. I had to cut-over to OpenSSL 1.1\n> due to deprecation of 1.0.2. OpenSSL 1.1 increased Perl requirements,\n> so now I have to build Perl, too. Previously I was not building Perl.\n> \n> I'm installing Perl 5.30.1, but it is a minimal install. I only\n> install Text::Template Test::More (plus whatever else Perl installs on\n> its own from cspan). However I could not install HTTP::Daemon\n> HTTP::Request. There's some bug in the cspan installer. It gets stuck\n> on one package and tries to download/install it over and over again.\n> \n> Do you know if Git is using one of Perl's Text:: packages for the test?\n\nI don't see any perl at all in t3902. The failing \"setup\" test is all\nshell, and is literally just doing \"echo stuff >$file_with_funny_chars\"\nin a loop.\n\n-Peff\n"},{"id":"391046","messageId":"20200203165318.eq3tjo5ja4pdjf7d@tb-raspi4","threadId":"52741","inReplyTo":"CAH8yC8=-ht7D3CyM-YoJSfW3hueaWVp5WQz2+BJOFMjmt8aDsg@mail.gmail.com","subject":"Re: Git 2.25 and failed self tests on OS X","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2020-02-03T16:53:18Z","receivedAt":"2020-02-03T16:53:30Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On Mon, Feb 03, 2020 at 06:00:18AM -0500, Jeffrey Walton wrote:\n> On Mon, Feb 3, 2020 at 3:43 AM Jeff King <peff@peff.net> wrote:\n> >\n> > On Sun, Feb 02, 2020 at 11:08:17PM -0500, Jeffrey Walton wrote:\n> >\n> > > I'm seeing some self-tests failures building the 2.25 release tarball\n> > > on OS X. I'm seeing it on the old PowerMac with OS X 10.5, and a\n> > > modern Intel Mac with OS X 10.9. PowerMac failures are not too\n> > > surprising, but the modern Mac should probably pass its self tests.\n> > >\n> > > *** t3902-quoted.sh ***\n> > > not ok 1 - setup\n> > > #\n> > > #\n> > > #               mkdir \"$FN\" &&\n> > > #               for_each_name \"echo initial >\\\"\\$name\\\"\" &&\n> > > #               git add . &&\n> > > #               git commit -q -m Initial &&\n> > > #\n> > > #               for_each_name \"echo second >\\\"\\$name\\\"\" &&\n> > > #               git commit -a -m Second &&\n> > > #\n> > > #               for_each_name \"echo modified >\\\"\\$name\\\"\"\n> >\n> > It's hard to see what's going on with this output. Try running:\n> >\n> >   ./t3902-quoted.sh -v -x -i\n> >\n> > to get more verbose output.\n> >\n> > Looking at this test, it tries to create files with funny characters in\n> > the names. Presumably your filesystem isn't happy with one or more of\n> > them. The verbose output will probably make it clear which.\n> >\n> > Version 10.9 isn't incredibly new, but these tests have been around a\n> > long time. If OS X has a problem with these filenames, it seems odd for\n> > it to be surfacing now.\n> >\n> > Do you know what filesystem you're using? You aren't running the tests\n> > by any chance on a network mount from a Windows machine?\n>\n> According to `diskutil info /`, the filesystem is Journaled HFS+. The\n> tests are running locally on the Mac after logging in over SSH.\n>\n> I'm wondering if Perl is the problem. I had to cut-over to OpenSSL 1.1\n> due to deprecation of 1.0.2. OpenSSL 1.1 increased Perl requirements,\n> so now I have to build Perl, too. Previously I was not building Perl.\n>\n> I'm installing Perl 5.30.1, but it is a minimal install. I only\n> install Text::Template Test::More (plus whatever else Perl installs on\n> its own from cspan). However I could not install HTTP::Daemon\n> HTTP::Request. There's some bug in the cspan installer. It gets stuck\n> on one package and tries to download/install it over and over again.\n>\n> Do you know if Git is using one of Perl's Text:: packages for the test?\n>\n> Jeff\n\nShooting out into the blue:\nWhich shell are you using when logging in via ssh ?\n\n\n\n"}]}