From: Thomas Gummerer <t.gummerer@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [BUG] test suite broken with GIT_TEST_SPLIT_INDEX
Date: Mon, 24 Apr 2017 23:15:16 +0100 [thread overview]
Message-ID: <20170424221516.GD4989@hank> (raw)
In-Reply-To: <CAP8UFD2f9g__ykCjReSoaAUvFTPmgRDbsWFQMRrFoFw8haV0uA@mail.gmail.com>
On 04/21, Christian Couder wrote:
> On Thu, Apr 20, 2017 at 11:24 PM, Thomas Gummerer <t.gummerer@gmail.com> wrote:
> > On 04/20, Christian Couder wrote:
> >>
> >> Could you try with the following patch:
> >>
> >> http://public-inbox.org/git/20170330210354.20018-1-chriscool@tuxfamily.org/
> >
> > Yeah, I tried with and without that patch with the same result.
> > Unless I'm screwing something up when testing I don't think this fixes
> > the issue unfortunately.
>
> I just tried on "pu" and only the first test
> (t7009-filter-branch-null-sha1.sh) fails there.
I can't seem to reproduce this now either with the latest pu or next.
I must have messed something up while testing.
Sorry for the noise.
next prev parent reply other threads:[~2017-04-24 22:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 20:52 [BUG] test suite broken with GIT_TEST_SPLIT_INDEX Thomas Gummerer
2017-04-20 21:03 ` Christian Couder
2017-04-20 21:24 ` Thomas Gummerer
2017-04-21 7:10 ` Christian Couder
2017-04-21 9:53 ` Duy Nguyen
2017-04-21 11:46 ` Christian Couder
2017-04-21 11:57 ` Christian Couder
2017-04-21 12:25 ` Duy Nguyen
2017-04-21 17:09 ` Jeff King
2017-04-21 14:25 ` Christian Couder
2017-04-21 15:23 ` Christian Couder
2017-04-21 17:05 ` Jeff King
2017-04-24 22:15 ` Thomas Gummerer [this message]
2017-04-21 4:01 ` Junio C Hamano
2017-04-21 7:02 ` Christian Couder
2017-04-20 21:06 ` 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=20170424221516.GD4989@hank \
--to=t.gummerer@gmail.com \
--cc=christian.couder@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.