[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Call stack with new testsuite logging?

From: Philip Martin <philip_at_codematters.co.uk>
Date: Wed, 14 Mar 2012 14:12:51 +0000

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'

It's not as easy to identify where in lock_tests.py the error is occurring.

Can we have the Python stack trace back?

-- 
Philip
Received on 2012-03-14 18:00:10 CET

This is an archived mail posted to the Subversion Dev mailing list.