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

Re: Probable bug with svn copy

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Mon, 25 Jan 2010 16:53:18 +0000

Paul Burba wrote:
> On Mon, Jan 25, 2010 at 2:17 AM, Noorul Islam K M <noorul_at_collab.net> wrote:
> > + # Move new added file to another one and commit.
> > + second_path = os.path.join(new_path, 'second')
> > + rav_svn(None, None, [], 'move', first_path, second_path)
> > + rav_svn(None, None, ["Committed revision 4.\n"], 'ci', '-m',
> ^^^^^^^^^^^^^^^^^^^^^^^^^
>
> The expected_stderr is "", not "Committed revision 4.\n". The
> expected_stdout is something like:
>
> [[[
> Adding svn-test-work\working_copies\copy_tests-77\A\New
> Adding svn-test-work\working_copies\copy_tests-77\A\New\second
>
> Committed revision 4.
> ]]]
>
> So you can either pass None as expected_stdout (in which case it isn't
> checked at all), pass a single string regex describing the above
> output, or use svntest.actions.run_and_verify_commit().

Oops, sorry, I already committed it in r902841. I'll change that or at
least add a comment.

> Also, would you mind taking a stab at expanding the test to cover
> Alan's original problem? Specifically that a second working copy,
> when updated, gets both the move destination *and* the source added.

Or a separate test - either way would be really helpful.

- Julian
Received on 2010-01-25 17:53:59 CET

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