From: Jonathan Nieder <jrnieder@gmail.com>
To: Adam Dinwoodie <adam@dinwoodie.org>
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: v2.15.0-rc1 test failure
Date: Wed, 11 Oct 2017 16:08:30 -0700 [thread overview]
Message-ID: <20171011230830.GA47665@aiede.mtv.corp.google.com> (raw)
In-Reply-To: <20171011223433.GA6079@dinwoodie.org>
Hi,
Adam Dinwoodie wrote:
> t0021.15 has PERL as a requirement, and I see semi-regular failures from
> Git tests that are Perl-based in one way or another (git-svn tests are
> the most common problems). I've not spotted t0021 failing in that way,
> but it sounds like the same class of problem.
>
> I dig into these failures when I see them, mostly by running the script
> a few hundred times until I get the failure again, and they've always
> been Perl itself segfaulting. That points to the problem being in
> Cygwin's Perl package rather than Git, and it's very unlikely to be
> anything that's got worse in v2.15.0.
That reminds me of https://bugs.debian.org/868738, which I tracked down
to perl's "die" helper using errno to determine the exit status instead
of deterministically using 128. I wasn't able to track it down further
than that.
t/t0021/rot13-filter.pl doesn't have any similar suspect constructs, but
thought I should mention it anyway.
Thanks,
Jonathan
next prev parent reply other threads:[~2017-10-11 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 22:15 v2.15.0-rc1 test failure Ramsay Jones
2017-10-11 22:25 ` Ramsay Jones
2017-10-11 22:34 ` Adam Dinwoodie
2017-10-11 23:08 ` Jonathan Nieder [this message]
2017-10-12 0:27 ` Ramsay Jones
2017-10-12 9:06 ` Adam Dinwoodie
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=20171011230830.GA47665@aiede.mtv.corp.google.com \
--to=jrnieder@gmail.com \
--cc=adam@dinwoodie.org \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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