Peter Samuelson <peter@p12n.org> writes:
>> I've checked the logs for error messages in the failed tests:
>>
>> >FAIL: lt-fs-base-test 2: open an existing Berkeley DB filesystem
>> ---
>> svn_tests: Berkeley DB error for filesystem 'test-repo-open-berkeley'
>> while opening environment:
>>
>> svn_tests: Invalid argument
>> svn_tests: bdb: DB_REGISTER limits each process to a single open DB_ENV
>> handle
> Well, a second build on ia64 produced the same error, so whatever it
> is, it's repeatable. The build daemon is using BDB 4.4.20, apr-util
> 0.9.7 (from apache 2.0.55),
>
> Any other ideas? Anyone?
Test 2 does open the repository twice but the second open should
simply retrieve the cached environment from Subversion's DB_ENV cache.
I can simulate the failure on i386 by using gdb to cause Subversion's
DB_ENV cache to fail: set a break point on line 654 of env.c and when
it stops there for the second time set bdb to zero and continue:
(gdb) r 2
Starting program: /home/pm/sw/subversion/obj/subversion/tests/libsvn_fs_base/.libs/lt-fs-base-test 2
Breakpoint 4, svn_fs_bdb__open (bdb_batonp=0x80709d8,
path=0x8051444 "test-repo-open-berkeley", flags=4571169, mode=438,
pool=0x8053d28) at ../svn/subversion/libsvn_fs_base/bdb/env.c:654
654 if (!bdb)
(gdb) c
Continuing.
Breakpoint 4, svn_fs_bdb__open (bdb_batonp=0x8083be0,
path=0x8051444 "test-repo-open-berkeley", flags=4571169, mode=438,
pool=0x8053d28) at ../svn/subversion/libsvn_fs_base/bdb/env.c:654
654 if (!bdb)
(gdb) set bdb = 0
(gdb) c
Continuing.
../svn/subversion/libsvn_fs_base/fs.c:543: (apr_err=160029)
svn_tests: Berkeley DB error for filesystem 'test-repo-open-berkeley' while opening environment:
../svn/subversion/libsvn_fs_base/bdb/bdb-err.c:59: (apr_err=160029)
svn_tests: Invalid argument
../svn/subversion/libsvn_fs_base/bdb/env.c:213: (apr_err=0)
svn_tests: bdb: DB_REGISTER limits each process to a single open DB_ENV handle
FAIL: lt-fs-base-test 2: open an existing Berkeley DB filesystem
I don't know why the DB_ENV cache would fail on ia64.
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 20 22:01:57 2006