[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r981905 - /subversion/trunk/subversion/tests/cmdline/depth_tests.py

From: Greg Stein <gstein_at_gmail.com>
Date: Tue, 3 Aug 2010 13:52:54 -0400

On Tue, Aug 3, 2010 at 13:41, Julian Foad <julian.foad_at_wandisco.com> wrote:
> Greg Stein wrote:
>> Why would this be true only in single-db? Shouldn't the test perform
>> exactly the same in both cases? I see no rationale for WHY these
>> should differ.
>>
>> On Tue, Aug 3, 2010 at 10:56,  <philip_at_apache.org> wrote:
>> > Make depth_tests.py 37-40 pass in single-db.
>> >
>> > * subversion/tests/cmdline/switc_tests.py
>> >  (make_depth_tree_conflicts): Tweak expectations for single-db.
> [...]
>> >   expected_disk.remove('A/mu',
>> >                        'A/B', 'A/B/lambda', 'A/B/E/alpha', 'A/B/E/beta',
>> >                        'A/D/gamma');
>> > +  if svntest.main.wc_is_singledb(sbox.wc_dir):
>> > +    expected_disk.remove('A/B/E', 'A/B/F')
>
> It's just because in single-db mode, deleted dirs really go away from
> disk, isn't it?

Beats me. Where is the comment to that effect? Where is the
explanation in the log message?

Why are these tests allowing *variant* outputs without any explanation?

-g
Received on 2010-08-03 19:53:30 CEST

This is an archived mail posted to the Subversion Dev mailing list.