All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Adam Dinwoodie <adam@dinwoodie.org>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: v2.15.0-rc1 test failure
Date: Thu, 12 Oct 2017 01:27:57 +0100	[thread overview]
Message-ID: <338656d4-182b-563f-9195-515d213d4b6d@ramsayjones.plus.com> (raw)
In-Reply-To: <20171011223433.GA6079@dinwoodie.org>



On 11/10/17 23:34, Adam Dinwoodie wrote:
[snip]
> Hi Ramsay,
> 
> I assume, given you're emailing me, that this is a Cygwin failure?

Yes, sorry, I should have made that clear.

> 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.

Yep, many moons ago, I used to run the svn tests (on Linux and cygwin)
which would fail intermittently on cygwin. I didn't notice any problem
with perl though.

> 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.

Since I stopped running the svn tests, the number of intermittent test failures on cygwin have dropped significantly, but haven't gone away
completely.

I just finished the second test-suite run and, of course, t0021 ran
without problem this time. Hmm, I don't think I have time to chase
this down at the moment. I will keep your 'perl hypothesis' in mind
for next time, however.

Thanks.

ATB,
Ramsay Jones



  parent reply	other threads:[~2017-10-12  0:28 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
2017-10-12  0:27   ` Ramsay Jones [this message]
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=338656d4-182b-563f-9195-515d213d4b6d@ramsayjones.plus.com \
    --to=ramsay@ramsayjones.plus.com \
    --cc=adam@dinwoodie.org \
    --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.