On Fri, Apr 21, 2017 at 2:10 PM, Christian Couder <christian.couder@xxxxxxxxx> wrote: > On Thu, Apr 20, 2017 at 11:24 PM, Thomas Gummerer <t.gummerer@xxxxxxxxx> wrote: >> On 04/20, Christian Couder wrote: >>> >>> Could you try with the following patch: >>> >>> http://public-inbox.org/git/20170330210354.20018-1-chriscool@xxxxxxxxxxxxx/ >> >> 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. > > Ok, I will take a look soon. > > By the way I think that GIT_TEST_SPLIT_INDEX has become redundant now > that there is core.splitIndex. > So perhaps in the long run it will be best to deprecate > GIT_TEST_SPLIT_INDEX and eventually remove it. I think you can't, at least the way I understand this variable. It's a _test_ variable to force exercise split index code path a whole lot more, by running the entire test suite with split index always enabled, instead of just a couple in t????-split-index.sh. We can't achieve the same with core.splitIndex because that's more about user control and you can't just set core.splitIndex for the entire test suite (can we?). I would understand if the failed tests are about core.splitIndex (they both try to control how split index is created), but failed tests look totally unrelated. We may have discovered some bug (or that git_path one Jeff mentioned). -- Duy