cmpilato_at_apache.org writes:
> Author: cmpilato
> Date: Thu Aug 9 16:16:07 2012
> New Revision: 1371282
>
> URL: http://svn.apache.org/viewvc?rev=1371282&view=rev
> Log:
> Fix a sandbox violation in prop_tests.py 35.
>
> * subversion/tests/cmdline/prop_tests.py
> (propget_redirection): Consult the controlled test-suite runtime
> config when invoking 'svn' directly.
>
> Modified:
> subversion/trunk/subversion/tests/cmdline/prop_tests.py
>
> Modified: subversion/trunk/subversion/tests/cmdline/prop_tests.py
> URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/tests/cmdline/prop_tests.py?rev=1371282&r1=1371281&r2=1371282&view=diff
> ==============================================================================
> --- subversion/trunk/subversion/tests/cmdline/prop_tests.py (original)
> +++ subversion/trunk/subversion/tests/cmdline/prop_tests.py Thu Aug 9 16:16:07 2012
> @@ -2268,7 +2268,7 @@ def propget_redirection(sbox):
>
> # Run propget -vR svn:mergeinfo, redirecting the stdout to a file.
> arglist = [svntest.main.svn_binary, 'propget', SVN_PROP_MERGEINFO, '-vR',
> - wc_dir]
> + '--config-dir', svntest.main.default_config_dir, wc_dir]
The user should be able to avoid the FAIL by having the appropriate
settings in their config and I'd like to document it in the release
notes.
I know that the test will be affected by a corrupt config. Is there a
config setting that affects propget? Was it your new password-store
that was unknown to 1.7?
--
Philip
Received on 2012-08-10 09:57:15 CEST