Re: test suite failures with 1.4.0

Thanks for the quick reply!

[Lieven Govaerts]
> >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
> ---
> Hm, I found a reference to this error message in this mail thread:
> http://svn.haxx.se/dev/archive-2006-03/0114.shtml
>
> Which talks about svn 1.3 not supporting BDB 4.4. You're not using old
> code or something? As far as I see in CHANGES DBD 4.4 is supported in
> svn 1.4.

Yes, this is 1.4.0, with a small collection of patches we have
accumulated. In case you're curious, the patches all live at
svn://svn.debian.org/pkg-subversion/trunk/debian/patches/. None are
related to db4.4.

> >FAIL: switch_tests.py 17: refresh the WC file system read-only attribute
> ---
> EXCEPTION: Failure: 'svn-test-work/working_copies/switch_tests-17/A/mu'
> expected to be read-only after having had its svn:needs-lock property set
> ---
> The test uses 'os.access(mu_path, os.W_OK)' to see if it can write
> that file, which it shouldn't be able to. This code is unchanged
> since svn 1.3. I've only seen this fail when running the tests as
> root.

Thanks, this's the hint I needed. For historical and arcane technical
reasons, our build process runs the testsuite as root on exactly those
three architectures.

I wonder why it never failed in 1.3 and before. Perhaps this is a new
test? In any case, I'll see if it is possible to rearrange our test
invocation to run during the non-root phase of the build. I don't see
any current reason not to do this, so I think it is merely historical.