From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Wincent Colaiuta <win@wincent.com>
Cc: "Benoit Sigoure" <tsuna@lrde.epita.fr>,
"Git Mailing List" <git@vger.kernel.org>,
"Väinö Järvelä" <v@pp.inet.fi>
Subject: Re: [BUG] t9101 (master) busted on Leopard
Date: Fri, 16 Nov 2007 13:48:50 +0100 [thread overview]
Message-ID: <20071116124850.GA14473@atjola.homenet> (raw)
In-Reply-To: <73246E38-9C22-4279-A53E-678434238E5C@wincent.com>
On 2007.11.16 12:00:02 +0100, Wincent Colaiuta wrote:
> El 15/11/2007, a las 22:13, Benoit Sigoure escribió:
>> Hi Wincent,
>> Can you reproduce this deterministically? If yes, can you re-run the test
>> with the --verbose flag and post the gzipped output (or send it to me if
>> the list doesn't like this sort of attachment).
>
> Inspecting the output of --verbose has allowed me to the point where things
> are failing; look at the very first test in t9101-git-svn-props.sh and
> witness the following:
>
> - before the test we are at revision 1
> - there are 3 "svn commits" in the test
> - but it looks like only 2 of the commits proceed
> - so the revision number goes up to 2 then 3, when it should be 4
> - as a result, in one of the later tests we fail because the test expects
> revision 8 but we only have revision 7
>
> Checked out revision 1.
> * ok 1: checkout working copy from svn
>
> * expecting success: cd test_wc &&
> echo Greetings >> kw.c &&
> poke kw.c &&
> svn commit -m "Not yet an Id" &&
> echo Hello world >> kw.c &&
> poke kw.c &&
> svn commit -m "Modified file, but still not yet an Id" &&
> svn propset svn:keywords Id kw.c &&
> poke kw.c &&
> svn commit -m "Propset Id" &&
> cd ..
> Sending kw.c
> Transmitting file data .
> Committed revision 2.
> Sending kw.c
> Transmitting file data .
> Committed revision 3.
> property 'svn:keywords' set on 'kw.c'
> * ok 2: setup some commits to svn
>
> That last commit is a no-op because, for some reason, the svn propset
> before it is also a no-op:
>
> svn propset svn:keywords Id kw.c
>
> In other words, it echos "property 'svn:keyword' set on 'kw.c'" but if I
> insert an "svn status" as the next command then I get no output at all. If
> I run the exact same commands manually from the terminal then they work
> (ie. it is not a no-op and "svn status" shows that the file is modified).
>
> Actually, it's not really a no-op, because if I insert an "svn proplist -v
> kw.c" I get:
>
> Properties on 'kw.c':
> svn:keywords : Id
It _is_ a no-op. At least here. Because I got an auto-props setting in
my ~/.subversion/config to automatically add Id for *.c files. So that
property was already there before we explicitly ask for it and the
propset turns into a no-op. If I remove that line from the subversion
configuration, the test succeeds. Same for you I guess.
That said, I had a quick glance over the subversion CLI help, but it
didn't tell me how to ignore/override ~/.subversion/config. Anyone less
clueless than me around, having a smart idea how to work around that
"bug"?
Björn
next prev parent reply other threads:[~2007-11-16 12:49 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 [this message]
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
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=20071116124850.GA14473@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=tsuna@lrde.epita.fr \
--cc=v@pp.inet.fi \
--cc=win@wincent.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