git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>,
	"Ævar Arnfjörð" <avarab@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: 1e633418479926bc85ed21a4f91c845a3dd3ad66 breaks on OSX
Date: Tue, 5 Oct 2010 21:45:18 -0400	[thread overview]
Message-ID: <20101006014518.GA8557@sigill.intra.peff.net> (raw)
In-Reply-To: <AANLkTimwRJ+X4Kom9_Nv-5Xjf1LKCPbkwavWYHqCdTaM@mail.gmail.com>

On Wed, Oct 06, 2010 at 12:33:20AM +0200, Sverre Rabbelier wrote:

> On Tue, Oct 5, 2010 at 23:34, Jeff King <peff@peff.net> wrote:
> > +ifndef NO_PERL
> > +all:: perl/perl.mak
> > +endif
> > +
> 
> Regardless of whether that fixes the problem that looks like a sane
> patch, so maybe we just should apply it?

I'm not opposed, though the situation is confusing enough I'd like to
have somebody confirm that my previous analysis makes sense (otherwise,
this is just adding cruft to the Makefile :) ).

Sadly, I can't seem to replicate the original problem, even doing
something like:

  n=1
  while true; do
    make clean;
    if ! make -j4; then break; fi
    echo $n; n=$(($n+1))
  done

(and I tried several variations). It ran for 20 minutes without failing.
My suspicion is that there may be some particular state that triggers
the race condition, but I can't seem to figure it out.

-Peff

      reply	other threads:[~2010-10-06  1:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 20:48 1e633418479926bc85ed21a4f91c845a3dd3ad66 breaks on OSX Randal L. Schwartz
2010-10-05 21:05 ` Ævar Arnfjörð Bjarmason
2010-10-05 21:13   ` Randal L. Schwartz
2010-10-05 21:34     ` Jeff King
2010-10-05 22:33       ` Sverre Rabbelier
2010-10-06  1:45         ` Jeff King [this message]

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=20101006014518.GA8557@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.com \
    --cc=srabbelier@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).