Philip Martin <phi...@codematters.co.uk> writes: > With the old testsuite code a test failure resulted in a Python stack > trace showing exactly where the error occurred. The new logging doesn't > appear to show it. So a failing test looks like: > > 2012-03-14 14:11:05 [INFO] CMD: svn unlock > svn-test-work/working_copies/lock_tests-8._b/iota --config-dir > /home/pm/sw/subversion/obj/subversion/tests/cmdline/svn-test-work/local_tmp/config > --password rayjandom --no-auth-cache --username jrandom > 2012-03-14 14:11:05 [INFO] <TIME = 0.041281> > 2012-03-14 14:11:05 [INFO] svn: warning: W160040: No lock on path '/iota' in > filesystem > '/home/pm/sw/subversion/obj/subversion/tests/cmdline/svn-test-work/repositories/lock_tests-8/db' > > 2012-03-14 14:11:05 [WARNING] svn: warning: W160040: No lock on path '/iota' > in filesystem > '/home/pm/sw/subversion/obj/subversion/tests/cmdline/svn-test-work/repositories/lock_tests-8/db'
I missed out the final line, after the above the output is: FAIL: lock_tests.py 8: verify behavior when a lock in a wc is defunct > > It's not as easy to identify where in lock_tests.py the error is occurring. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
