Alan Fry wrote on Tue, 01 Dec 2020 03:02 +00:00:
> On Mon, Nov 30, 2020 at 9:15 PM Alan Fry <ttlx0100_at_gmail.com> wrote:
> > After some digging and using the references from this group, I'm down to just one error in the fails file (below). I'm still digging into this. Does anyone have hints on where / what library might cause this one to fault? Since this is clearly a low level call, I'm assuming that some prerequisite is the issue. This is on the linux build.
> > I have all the helpful hints for the Windows build, once I get some time to work on that, I'll create a seperate thread.
> > [[[
> > subversion/tests/libsvn_fs/locks-test.c:1134: (apr_err=SVN_ERR_TEST_FAILED)
> > svn_tests: E200006: Expected error but got SVN_NO_ERROR
> > FAIL: locks-test 14: lock/unlock when 'write-lock' couldn't be obtained
> > ]]]
> This is an interesting fault.
> The test is to lock paths and generate an error. In my build, it
> fails... because the svn_fs_lock_many call returns success.
> /* Trying to lock some paths. We don't really care about error; the test
> shouldn't crash. */
> target = svn_fs_lock_target_create(NULL, newrev, pool);
> lock_paths = apr_hash_make(pool);
> svn_hash_sets(lock_paths, "/iota", target);
> svn_hash_sets(lock_paths, "/A/mu", target);
> SVN_TEST_ASSERT_ANY_ERROR(svn_fs_lock_many(fs, lock_paths, "comment", 0, 0, 0,
> lock_many_cb, &baton, pool, pool));
Read the comment immediately above the function you quoted that code from.
If that's not it, run «mount» without arguments (it may not be in $PATH)
and post the lines of output that pertain to the build directory (the
one you ran «./configure» in) and to its subdirectories.
Received on 2020-12-01 18:59:54 CET