From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Brian Gernhardt <brian@gernhardtsoftware.com>,
"git@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: t3010 broken by 2eac2a4
Date: Thu, 22 Aug 2013 16:54:10 -0400 [thread overview]
Message-ID: <CAPig+cQHTvmTWvGfg1Z3KfBrPD+QbSEbYBYz6XWT3KKu3-+jyQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqbo4qu3g4.fsf@gitster.dls.corp.google.com>
On Wed, Aug 21, 2013 at 5:41 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Brian Gernhardt <brian@gernhardtsoftware.com> writes:
>
>> With 2eac2a4: "ls-files -k: a directory only can be killed if the index has a non-directory" applied, t3010 fails test 3 "validate git ls-files -k output". It ends up missing the pathx/ju/nk file.
>>
>> OS X 10.8.4
>> Xcode 4.6.3
>> clang "Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)"
>
> Very interesting, as it obviously does not reproduce for me.
I can confirm this failure on OS X, however, I am somewhat confused by
the follow-up t3010 changes in 3c56875176390eee. Are the t3010 changes
supposed to fail without 2eac2a4cc4bdc8d7 applied? For me, on Linux,
the tests succeed whether 2eac2a4cc4bdc8d7 is applied or not. On OS X,
the tests succeed without 2eac2a4cc4bdc8d7 but fail with it applied.
next prev parent reply other threads:[~2013-08-22 20:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 20:31 t3010 broken by 2eac2a4 Brian Gernhardt
2013-08-21 21:41 ` Junio C Hamano
2013-08-22 20:54 ` Eric Sunshine [this message]
2013-08-22 21:16 ` Junio C Hamano
2013-08-22 21:22 ` Eric Sunshine
2013-08-22 21:32 ` Junio C Hamano
2013-08-22 21:35 ` Eric Sunshine
2013-08-22 21:43 ` Junio C Hamano
2013-08-22 21:59 ` Eric Sunshine
2013-08-22 22:53 ` Eric Sunshine
2013-08-22 23:12 ` Junio C Hamano
2013-08-22 23:15 ` Eric Sunshine
2013-08-23 4:32 ` Eric Sunshine
2013-08-23 5:36 ` Junio C Hamano
2013-08-23 9:19 ` Eric Sunshine
2013-08-23 17:15 ` Junio C Hamano
2013-08-23 18:51 ` Jeff King
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=CAPig+cQHTvmTWvGfg1Z3KfBrPD+QbSEbYBYz6XWT3KKu3-+jyQ@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).