From: Jeff King <peff@peff.net>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: 1e633418479926bc85ed21a4f91c845a3dd3ad66 breaks on OSX
Date: Tue, 5 Oct 2010 17:34:02 -0400 [thread overview]
Message-ID: <20101005213401.GA22845@sigill.intra.peff.net> (raw)
In-Reply-To: <86iq1g2vhq.fsf@red.stonehenge.com>
On Tue, Oct 05, 2010 at 02:13:53PM -0700, Randal L. Schwartz wrote:
> >>>>> "Ævar" == Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
> Ævar> 1e63341 is a merge commit, and none of the merged things (in the
> Ævar> commit message) seem to have anything to do with the Perl makefile
> Ævar> process.
>
> Ævar> Can you run:
>
> Ævar> make -j 1 V=1
>
> Ævar> And report what output you get?
>
> Oddly enough, just rerunning the make again *worked*.
>
> That's scary.
>
> And therefore also not bisectable. :(
>
> I imagine there's some heisenbug in there, that we'll probably trip over
> later.
This has come up before, but nobody has managed to track it down. I did
some looking at it in the past, but this is all I could find:
http://article.gmane.org/gmane.comp.version-control.git/117710
If my analysis there is right, we could probably protect against it with
something like:
diff --git a/Makefile b/Makefile
index 25f94b0..aaef528 100644
--- a/Makefile
+++ b/Makefile
@@ -1596,6 +1596,10 @@ ifndef NO_PYTHON
endif
$(QUIET_SUBDIR0)templates $(QUIET_SUBDIR1) SHELL_PATH='$(SHELL_PATH_SQ)' PERL_PATH='$(PERL_PATH_SQ)'
+ifndef NO_PERL
+all:: perl/perl.mak
+endif
+
please_set_SHELL_PATH_to_a_more_modern_shell:
@$$(:)
But of course it's hard to test.
-Peff
next prev parent reply other threads:[~2010-10-05 21:33 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 [this message]
2010-10-05 22:33 ` Sverre Rabbelier
2010-10-06 1:45 ` Jeff King
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=20101005213401.GA22845@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.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).