Hi Dscho,
On Sat, Jul 7, 2018 at 5:11 AM, Johannes Schindelin
<johannes.schinde...@gmx.de> wrote:
> Hi Elijah,
>
> On Fri, 6 Jul 2018, Elijah Newren wrote:
>
>> On Fri, Jul 6, 2018 at 3:57 PM, Junio C Hamano <gits...@pobox.com> wrote:
>> > I'll be pushing out the integration branches with some updates, but
>> > there is no change in 'next' and below. The following topics I gave
>> > a quick look and gave them topic branches, but I had trouble merging
>> > them in 'pu' and making them work correctly or pass the tests, so
>> > they are not part of 'pu' in today's pushout.
>> >
>> > pk/rebase-in-c
>> > en/dirty-merge-fixes
>> > en/t6036-merge-recursive-tests
>> > en/t6042-insane-merge-rename-testcases
>> > ds/multi-pack-index
>>
>> It looks to me like the main problem is that pu itself has lots of
>> test failures. It seems to bisect down to
>> kg/gc-auto-windows-workaround. If I revert commit ac9d3fdbebbd ("gc
>> --auto: clear repository before auto packing", 2018-07-04), then pu
>> passes tests again for me.
>
> Is this the segmentation fault about which I just sent a mail?
Yes, this is is a gc segfault issue. It looks like every test calling
git gc will fail because of it, I even saw a "nothing to pack" message
or something like that followed by a segfault.
