On Sep 12, 2007, at 10:48 PM, lgo@tigris.org wrote:
...
> Fix random Windows buildbot errors: the tests currently cache the
> credentials,
> but when running the tests in parallel you can't rely on them being
> the
> credentials you expect. Solution is to always explicitly pass the
> credentials
> you want to use.
>
> * subversion/tests/cmdline/lock_tests.py
> (commit_propchange): specify username and password for the commit.
>
>
> Modified:
> trunk/subversion/tests/cmdline/lock_tests.py
>
> Modified: trunk/subversion/tests/cmdline/lock_tests.py
> URL: http://svn.collab.net/viewvc/svn/trunk/subversion/tests/
> cmdline/lock_tests.py?pathrev=26574&r1=26573&r2=26574
> ======================================================================
> ========
> --- trunk/subversion/tests/cmdline/lock_tests.py (original)
> +++ trunk/subversion/tests/cmdline/lock_tests.py Wed Sep 12
> 22:48:21 2007
> @@ -181,7 +181,10 @@
>
> # make a property change and commit it, allowing lock to be
> released
> svntest.main.run_svn(None, 'propset', 'blue', 'azul', file_path)
> - svntest.main.run_svn(None, 'commit', '-m', '', file_path)
> + svntest.main.run_svn(None, 'commit',
> + '--username', svntest.main.wc_author,
> + '--password', svntest.main.wc_passwd,
> + '-m', '', file_path)
...
Is this necessary anywhere that we use run_svn()? I just added more
usage of it to actions.py...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 13 19:18:16 2007