From: "Torsten Bögershausen" <tboegi@web.de>
To: git@vger.kernel.org
Cc: "Torsten Bögershausen" <tboegi@web.de>
Subject: t7400 broken on pu (Mac OS X)
Date: Wed, 09 Jan 2013 19:43:03 +0100 [thread overview]
Message-ID: <50EDBA37.30205@web.de> (raw)
The current pu fails on Mac OS, case insensitive FS.
Bisecting points out
commit 3f28e4fafc046284657945798d71c57608bee479
[snip]
Date: Sun Jan 6 13:21:07 2013 +0700
Convert add_files_to_cache to take struct pathspec
And I veryfied that the preceeding commit 05647d2d8a5dc456d1f4ef73
is OK.
It fails here:
not ok 38 - gracefully add submodule with a trailing slash
A run of a modified t7400 looks like this:
Is there anything more, that I can do to debug this?
[snip]
ok 37 - do not add files from a submodule
expecting success:
git reset --hard &&
echo 1 >&2 &&
git commit -m "commit subproject" init &&
echo 2 >&2 &&
(cd init &&
echo 3 >&2 &&
echo b > a) &&
echo 4 >&2 &&
git add init/ &&
echo 5 >&2 &&
git diff --exit-code --cached init &&
echo 6 >&2 &&
commit=$(cd init &&
echo 7 >&2 &&
git commit -m update a >/dev/null &&
echo 8 >&2 &&
git rev-parse HEAD) &&
echo 9 >&2 &&
git add init/ &&
echo 10 >&2 &&
test_must_fail git diff --exit-code --cached init &&
echo 11 >&2 &&
test $commit = $(git ls-files --stage |
sed -n "s/^160000 \([^ ]*\).*/\1/p")
HEAD is now at 57f2622 super commit 1
1
[second 1b8c63f] commit subproject
Author: A U Thor <author@example.com>
1 file changed, 1 insertion(+), 1 deletion(-)
2
3
4
5
6
7
8
9
10
test_must_fail: command succeeded: git diff --exit-code --cached init
not ok 38 - gracefully add submodule with a trailing slash
next reply other threads:[~2013-01-09 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 18:43 Torsten Bögershausen [this message]
2013-01-09 19:16 ` t7400 broken on pu (Mac OS X) Junio C Hamano
2013-01-10 6:28 ` Duy Nguyen
2013-01-10 17:58 ` Junio C Hamano
2013-01-10 19:06 ` Torsten Bögershausen
2013-01-11 11:03 ` Duy Nguyen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50EDBA37.30205@web.de \
--to=tboegi@web.de \
--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.
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 NNTP newsgroup(s).