From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: A Large Angry SCM <gitzilla@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Latest master failing t7401 submodule tests
Date: Wed, 3 Mar 2010 15:02:39 -0500 [thread overview]
Message-ID: <20100303200239.GA28904@coredump.intra.peff.net> (raw)
In-Reply-To: <7vhboxqje8.fsf@alter.siamese.dyndns.org>
On Wed, Mar 03, 2010 at 11:45:19AM -0800, Junio C Hamano wrote:
> A Large Angry SCM <gitzilla@gmail.com> writes:
>
> > 13 to the 18 tests in t7401 submodule test jig are failing with the
> > latest master this morning.
>
> Do you mean v1.7.0.1-138-ga75bab5?
>
> I don't see it with Debian 5.0.4 on x86_64 (my primary box), Fedora 11 nor
> FreeBSD 8.0 (the latter two are kvm sandboxes pretending to be i686).
I did see it on my debian unstable box with with dash as /bin/sh (though
IIRC, isn't FreeBSD /bin/sh ash?). It looked like a "shift: can't shift
that many" error, but I haven't had time to track it down further yet
(I'm installing lighting in a 2-year-old's play kitchen. ;) ).
Maybe the shell selection will give somebody lead. If not, I'll try to
look at it again in a few hours.
-Peff
next prev parent reply other threads:[~2010-03-03 20:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 12:21 Latest master failing t7401 submodule tests A Large Angry SCM
2010-03-03 19:45 ` Junio C Hamano
2010-03-03 20:02 ` Jeff King [this message]
2010-03-03 20:32 ` Junio C Hamano
2010-03-03 20:42 ` Jeff King
2010-03-03 21:04 ` Junio C Hamano
2010-03-03 21:28 ` Junio C Hamano
2010-03-03 21:58 ` What should "git submodule summary" give before an initial commit? Junio C Hamano
2010-03-03 23:10 ` Johan Herland
2010-03-04 0:36 ` Jens Lehmann
2010-03-04 6:01 ` Sverre Rabbelier
2010-03-04 6:22 ` Junio C Hamano
2010-03-04 6:36 ` Sverre Rabbelier
2010-03-04 6:43 ` Junio C Hamano
2010-03-04 6:48 ` Sverre Rabbelier
2010-03-03 22:57 ` Latest master failing t7401 submodule tests Jeff King
2010-03-03 20:52 ` 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=20100303200239.GA28904@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitzilla@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).