From: Kim Gybels <kgybels@infogroep.be>
To: Elijah Newren <newren@gmail.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Junio C Hamano" <gitster@pobox.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Nguyễn Thái Ngọc" <pclouds@gmail.com>
Subject: Re: What's (not) cooking
Date: Sun, 8 Jul 2018 00:54:45 +0200 [thread overview]
Message-ID: <20180707225445.GA6152@infogroep.be> (raw)
In-Reply-To: <CABPp-BHRE5ygBaXEkrmB_2-YKhq2Mr_Hr9Mg4PbUK_8-EmYU+Q@mail.gmail.com>
On (07/07/18 08:34), Elijah Newren wrote:
> Hi Dscho,
>
> On Sat, Jul 7, 2018 at 5:11 AM, Johannes Schindelin
> <Johannes.Schindelin@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 <gitster@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.
Sorry, I forgot to run the tests for v2 of my patch. I'll be more
careful in the future.
-Kim
next prev parent reply other threads:[~2018-07-07 23:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 22:57 What's (not) cooking Junio C Hamano
2018-07-06 23:07 ` Junio C Hamano
2018-07-07 2:16 ` Elijah Newren
2018-07-07 12:11 ` Johannes Schindelin
2018-07-07 15:34 ` Elijah Newren
2018-07-07 22:54 ` Kim Gybels [this message]
2018-07-07 12:08 ` Johannes Schindelin
2018-07-09 13:50 ` Derrick Stolee
2018-07-09 16:13 ` Junio C Hamano
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=20180707225445.GA6152@infogroep.be \
--to=kgybels@infogroep.be \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=pclouds@gmail.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).