On 4/27/06, rooneg@tigris.org <rooneg@tigris.org> wrote:
> Author: rooneg
> Date: Thu Apr 27 10:18:09 2006
> New Revision: 19462
>
> Modified:
> trunk/subversion/tests/cmdline/README
> trunk/subversion/tests/cmdline/authz_tests.py
> trunk/subversion/tests/cmdline/davautocheck.sh
> trunk/subversion/tests/cmdline/svnsync_tests.py
> trunk/subversion/tests/cmdline/svntest/main.py
> trunk/subversion/tests/cmdline/svntest/testcase.py
> trunk/tools/test-scripts/svntest/mod_dav_svn.conf
>
> Log:
> Turn on mod_authz_svn for tests over DAV. We have several tests that
> exercise our authz functionality, but up to now they have only been run
> over ra_svn, since our ra_dav tests have not been configured to use
> mod_authz_svn. Since our test suite does not provide us with the ability
> to change httpd.conf for a single test, that means we need to turn it on
> for all tests, with a default authz file that just gives anyone full read
> write access to the repository, just like they had without mod_authz_svn.
>
> Note: Anyone who's been running the DAV tests without using davautocheck
> will have to tweak their httpd.conf to make things work again.
>
> * subversion/tests/cmdline/svnsync_tests.py
> (basic_authz): Pass a name to sbox.build(), and move the writing of
> the authz conf file later in the test so it doesn't get overwritten.
> (copy_from_unreadable_dir): Ditto, but also make the authz file
> conditional on the type of ra layer we're using.
Garret, it seems you broke dav testsuite on clean machine, i.e. where
svn-test-work directory doesn't left from previous tests. Because you
are trying to create authz file when svn-test-work directory may be
doesn't exists. It will be create indirectly latter (when repository
will be created).
For sure, just try remove svn-test-work dir and execute test suite
over ra_dav. I'm not Subversion test suite expert and might be problem
in something else.
[...]
--
Ivan Zhakov
Received on Wed May 10 10:36:38 2006