From: Jeffrey Walton <noloader@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: Git 2.25 and failed self tests on OS X
Date: Sun, 2 Feb 2020 23:08:17 -0500 [thread overview]
Message-ID: <CAH8yC8kXPi0teqdZ8NRJ677Z6btbmdafR=y4MFFaKZgZrB=d4A@mail.gmail.com> (raw)
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
next reply other threads:[~2020-02-03 4:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 4:08 Jeffrey Walton [this message]
2020-02-03 8:43 ` Git 2.25 and failed self tests on OS X Jeff King
2020-02-03 11:00 ` Jeffrey Walton
2020-02-03 11:06 ` Jeff King
2020-02-03 16:53 ` Torsten Bögershausen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8yC8kXPi0teqdZ8NRJ677Z6btbmdafR=y4MFFaKZgZrB=d4A@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).