switch_tests.py fails -- a new variant?

[George Reeke <re...@mail.rockefeller.edu>]

To the list:
I am trying to install subversion 1.4.6 on a RedHat EL 4.6 system.
After a successful configure and make, the 'make check' (running as
root) gives exactly the following error and a bunch of tests skipped:

At least one test FAILED, checking /opt/subversion-1.4.6/tests.log
FAIL:  switch_tests.py 17: refresh the WC file system read-only
attribute
At least one test was SKIPPED, checking /opt/subversion-1.4.6/tests.log
.....

I searched the archives and found many people had this problem, usually
with many other failures--I had just the one.  The suggestion was not to
run as root.  So I tried to run 'make check' as an ordinary user.  Then
I got what looked like permissions problems right away, so I went back
as root, did 'chmod -R a+w *' in the subversion home directory, back to
ordinary user, run 'make check' again, now almost every test failed.
So it seems I have a different problem than those other posters.

Can someone tell me what this test means (what is a WC file system?),
can I ignore it, or if not, what do I need to do to fix it?

Details:
I updated the apr supplied by RedHat to 1.2.12 as required and added
apr-util-1.2.12 to my system.  As far as I can recall, no errors
in the make or make check for either package.
I plan to use subversion with the built-in database and web server,
so I ran the configure with these options:
./configure --without-berkeley-db --with-apr=/opt/apr-1.2.12 \
   --with-apr-util=/opt/apr-util-1.2.12 \
   --without-apache --without-apxs --without-neon --without-serf
The configure gave a warning that swig was not up to date, so I
removed the swig supplied by RedHat and installed version 1-3-29,
the last one the subversion instructions said was supported.  The
'make check' for this package gave numerous failures, but the tests
for perl and python seemed OK, and I did not expect to use these
or any of the other supported languages except C and C++, so I
ignored these errors.  I have no idea what swig is for, but it is
not listed as required for subversion, so I am assuming the swig
test failures are not the cause of my subversion error.

Thanks for any help,
George Reeke



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org