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

Re: [PATCH] More tests for the svn.wc Python bindings

From: David James <djames_at_collab.net>
Date: 2006-06-16 04:35:49 CEST

> Madan U Sreenivasan wrote:
> > Why is the class called SubversionRepositoryTestCase? Shouldn't it be
> > SubversionWorkingCopyTestCase?

Good point. Yeah, that'd be better.

> > Also, am not sure about this, but wont it be much clearer, if the log file
> > referred to the functions with the class.function() convention?

If the file in question contains only one class, you can just use the
function name.

> > ---------------------8<---------------------------------8<------------------
> > madan@madan ~/wc/trunk $ gdb --args python2.4
> > ./subversion/bindings/swig/python/tests/wc.py
> > #0 0x4048180e in apr_palloc () from /usr/lib/libapr-0.so.0
> > #1 0x4066f8dc in create_svn_repos_t (path=0x403ef3c4
> > "/tmp/trac-svnrepos", pool=0x0) at repos.c:1540
> > #2 0x4066fc00 in svn_repos_create (repos_p=0x0, path=0x403ef3c4
> > "/tmp/trac-svnrepos", unused_1=0x402b90ac "",
> > unused_2=0x402b90ac "", config=0x0, fs_config=0x0, pool=0x0) at
> > repos.c:1664
> > #3 0x408f368a in ?? () from
> > /usr/lib/python2.4/site-packages/libsvn/_repos.so

Oops. You're using an old version of the Python bindings with a new
version of Subversion. I can tell this from the stack trace because
your Subversion build has debug symbols but your Python bindings build
does not. Also, I can see that you're running Python bindings from
'/usr/lib', and it is unusual to keep your trunk bindings in
'/usr/lib'.

Madan, have you tried running the regular 'make check-swig-py' target?
This target automatically sets up your Python path so that the tests
will run with the version of the Python bindings in your build tree.
You may also need to run 'make clean-swig && ./configure' if you want
to get a completely clean build.

> > I will try with my laptop at office today... looking at the bt, I
> > suspect linkages with older versions of libapr... what do you think?
> I'm not sure - if pool=NULL is a valid argument to create_svn_repos_t(),
> then at least the Python bindings are not to blame. This must've been
> broken longer though - this is code that's being called from the trac
> test cases.

pool=NULL is not a valid argument to create_svn_repos_t or svn_repos_create.

> I'm using libapr-1 (you appear to be using libapr-0), so you might want
> to try that version. Is subversion supposed to work with any particular
> version of libapr or should any do?

Subversion should work with either libapr-1 or libapr-0.

Cheers,

David

-- 
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 16 04:36:26 2006

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