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

Re: Test failures since updating past the merge of locking

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2005-04-01 19:12:58 CEST

On Fri, 1 Apr 2005, Julian Foad wrote:

> Since updating about a week ago after the locking branch was merged, I have
> updated and re-run autogen.sh, configure, etc., but I am getting severeal
> test failures. Is there something else I need to do?
> These failures occur with both "make check" and "make svncheck":
> FAIL: lt-locks-test 1: lock only
> FAIL: lt-locks-test 2: lookup lock by path
> FAIL: lt-locks-test 3: attach lock
> FAIL: lt-locks-test 4: get locks
> FAIL: lt-locks-test 5: basic locking
> FAIL: lt-locks-test 6: test that locking requires proper credentials
> FAIL: lt-locks-test 7: test that locking is enforced in final commit step
> FAIL: lt-locks-test 8: dir propchange can be committed with locked child
> FAIL: lt-locks-test 11: test that locks can expire
> FAIL: lt-locks-test 12: breaking, stealing, refreshing a lock
> FAIL: lt-locks-test 13: check out-of-dateness before locking
> FAIL: lt-ra-local-test 1: open an ra session to a local repository
> FAIL: lt-ra-local-test 2: get the youngest revision in a repository
> FAIL: lt-ra-local-test 6: test svn_ra_local__split_URL correctness
> FAIL: lt-repos-test 1: test svn_repos_dir_delta
> FAIL: lt-repos-test 2: test deletions under copies in node_tree code
> FAIL: lt-repos-test 3: test svn_repos_history() (partially)
> FAIL: lt-repos-test 4: test svn_repos_node_locations
> FAIL: lt-repos-test 5: test removal of defunct locks
> I have always been using BDB in the past. I'm not sure if the recent
> discussion about making FSFS the default is relevant, but I have not altered
> my build/test script. I configured with:
> cd /home/julianfoad/build/subversion/
> CFLAGS=-Wall -Wundef -Wendif-labels -Wcast-qual -Wstrict-prototypes
> -Wmissing-prototypes -Wredundant-decls -Wnested-externs
> /home/julianfoad/src/subversion/configure --with-apxs=/usr/sbin/apxs2
> --enable-maintainer-mode --disable-mod-activation
> conftest.c:28: warning: function declaration isn't a prototype
> configure: WARNING: no JNI header files found.
> The test log of the first failure is:
> START: locks-test
> /home/julianfoad/src/subversion/subversion/libsvn_subr/io.c:1628:
> (apr_err=39)
> svn: Can't remove 'test-repo-lock-only': Directory not empty

I had this same problem, (I think), last night, see my posts from last
night. I found out that the first time the test is run it runs
succesfully, then the next times it fails with that error (even if no BDB
is being compiled, i.e., FSFS only.

However, when I told my build process to "make check CLEANUP=true" then
all the tests now pass and I was able to get a good build for the first
time in a week.

    - David

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 1 19:14:09 2005

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