Ben Collins-Sussman wrote:
> Looking at your tests.log, it seems that the test failures are related
> to situations whereby a file should be locally modified, but subversion
> isn't detecting the modification.
>
> Are you perhaps running the tests on a FAT filesystem? FAT has a 2-
> second time resolution for timestamps, so it's possible that a script
> can append to a file and then ask 'svn' to stat the file all within 2
> seconds. Subversion sees no change in timestamp, so it assumes that
> the file hasn't changed.
>
>
>
No, this is on a Linux x86 system (shared hosting machine). I won't be
creating/using berkeley-db type repositories, just fsfs somewhere below
my home directory on the web hoster.
In any event, I've now done this test at least 3 times:
rm -rf subversion-1.2.1
tar zxf subversion-1.2.1.tar.gz
cd subversion-1.2.1
./configure --prefix=/home/myhome/opt --without-berkeley-db --with-ssl
--with-zlib
make
make fsfscheck
And each time the last make step gives different test failures!
But I had forgotten that the hosting company keeps home directories
mounted via NFS--as soon as I did the same build procedure on the
hosting machine in /usr/local/tmp (locally mounted ext3 filesystem), all
tests passed O.K.
So, sorry to have bothered the mailing list with this, which is
mentioned somewhere in the build instructions.
I notice that the FAQ addresses the problem of NFS Subversion fsfs
repositories on Linux by suggesting that such NFS shares be mounted with
subtree checking disabled, something which I doubt I can convince the
hosting company to try... is there any other way around this particular
Linux/Subversion problem?
--
Insert Real Name
insertrealname AT yahoo.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 18 05:11:24 2005