On Fri, Jul 17, 2009 at 01:39:12PM +0800, HuiHuang wrote:
> Hey Stefan,
> >When I run the tests I get failures, however.
> >Do you get these failures, too?
> No, I pass the test successfully. See below:
> CMD: svn.exe commit -m log "svn-test-work\working_copies\commit_tests-1" "svn-test-work\working_copies\commit_tests-1\A\wc2" --config-dir "E:\newSVN\Release\subversion\tests\cmdline\svn-test-work\local_tmp\config" --password rayjandom --no-auth-cache --username jrandom
> <TIME = 0.922000>
> Sending svn-test-work\working_copies\commit_tests-1\A\mu
> Transmitting file data .Sending svn-test-work\working_copies\commit_tests-1\A\wc2\A\B\lambda
> Committed revision 2.
> Committed revision 3.
> PASS: commit_tests.py 1: commit from two nested working copies
> CLEANUP: svn-test-work\working_copies\commit_tests-1
> CLEANUP: svn-test-work\repositories\commit_tests-1
> PASS: commit_tests.py 2: commit from two working copies
> CLEANUP: svn-test-work\working_copies\commit_tests-2
> CLEANUP: svn-test-work\repositories\commit_tests-2
Interesting. Then we'll need to figure out what the difference
is between what's done on Windows and what's done on Linux.
> >$ ./commit_tests.py commit_multiple_wc_nested commit_multiple_wc
> >subversion/svn/commit-cmd.c:144: (apr_err=200000)
> >subversion/libsvn_client/commit.c:2015: (apr_err=200000)
> >subversion/libsvn_client/commit.c:1669: (apr_err=200000)
> >subversion/libsvn_client/commit.c:1637: (apr_err=200000)
> >svn: '/home/stsp/svn/svn-trunk/subversion/tests/cmdline/svn-test-work/working_copies/commit_tests-25/A/wc2' cannot be locked
> Is this path the right path? Should not it be
> Under windows the test case is under *Release* dir and the path is like this:
No that path is fine, there is no "Release" dir when compiling on Linux.
Received on 2009-07-17 11:30:59 CEST