From: Wincent Colaiuta <win@wincent.com>
To: "Väinö Järvelä" <v@pp.inet.fi>
Cc: Brian Gernhardt <benji@silverinsanity.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [BUG] t9101 (master) busted on Leopard
Date: Fri, 16 Nov 2007 11:17:03 +0100 [thread overview]
Message-ID: <EBFD3ABD-CD7F-4B9C-AB9D-F440C368AB61@wincent.com> (raw)
In-Reply-To: <4207CF02-36BD-4733-9861-17B0C4DB9D94@pp.inet.fi>
El 16/11/2007, a las 9:59, Väinö Järvelä escribió:
> On Nov 16, 2007, at 10:37, Wincent Colaiuta wrote:
>
>> Strange. I've looked in the environment and there is nothing
>> suspicious; in fact, running the tests with a totally clean
>> environment (env -i ./t9101-git-svn-props.sh) produces exactly the
>> same result.
>>
>> This was with commit 039bc64e (HEAD of master yesterday). I just
>> tested the commit you mention (HEAD of next) and get the same
>> failure; this is the procedure I'm using to test:
>>
>> git fetch
>> git checkout -b next_test origin/next
>> git describe # (v1.5.3.5-1780-gca2b71c)
>> git clean
>> make clean && make
>> cd t
>> env -i ./t9101-git-svn-props.sh
>>
>> So really, not sure what could be causing this.
>
> Did you forget to install the newly compiled version? Or does the
> test system use git from the source tree?
I didn't install the newly compiled version because, as far as know,
the test system uses the built copy in the source tree (I can't
actually recall *any* Makefile-based open source projects that didn't
work like that).
$ git --version
git version 1.5.3.5
$ /usr/local/bin/git --version
git version 1.5.3.5
$ ./git --version # (from inside the source tree)
git version 1.5.3.5.1780.gca2b
$ env -i git --version
env: git: No such file or directory
So the test run above *must* be using the just-built copy in the
source tree otherwise *none* of the tests would pass.
Cheers,
Wincent
prev parent reply other threads:[~2007-11-16 10:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 13:46 [BUG] t9101 (master) busted on Leopard Wincent Colaiuta
2007-11-15 16:04 ` Brian Gernhardt
2007-11-15 16:11 ` Wincent Colaiuta
2007-11-15 21:13 ` Benoit Sigoure
2007-11-15 22:22 ` Wincent Colaiuta
2007-11-16 11:00 ` Wincent Colaiuta
2007-11-16 12:48 ` Björn Steinbrink
2007-11-16 13:14 ` [PATCH] " Wincent Colaiuta
2007-11-16 13:25 ` [PATCH] Fix t9101 test failure caused by Subversion "auto-props" Wincent Colaiuta
2007-11-16 17:56 ` Benoit Sigoure
2007-11-17 0:19 ` Junio C Hamano
2007-11-17 13:28 ` Wincent Colaiuta
2007-11-16 4:25 ` [BUG] t9101 (master) busted on Leopard Väinö Järvelä
2007-11-16 8:37 ` Wincent Colaiuta
2007-11-16 8:59 ` Väinö Järvelä
2007-11-16 10:17 ` Wincent Colaiuta [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=EBFD3ABD-CD7F-4B9C-AB9D-F440C368AB61@wincent.com \
--to=win@wincent.com \
--cc=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
--cc=v@pp.inet.fi \
/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).