Re: testsuite failues of 1.0.9 on GNU/Linux sparc/ia64

> Is that like NFS, or something else?

It is a local filesystem, this one happens to be ext3. The 'bind'
mount is a way of making a filesystem appear in more than one location
in a directory tree. For example, one can 'mount' /home/ on
/chroots/unstable/home/ so that processes that have done :

# chroot /chroots/unstable

will still have access to /home/. Actually, the manpage explains
better than I:

       Since Linux 2.4.0 it is possible to remount part of the file
       hierarchy somewhere else. The call is
              mount --bind olddir newdir
       After this call the same contents is accessible in two places.

I haven't looked at how the 'bind' mount is implemented but I _think_
that the testsuite failures are a filesystem problem, we have errors
like:

START: run-repos-tests.py
Traceback (most recent call last):
  File "/build/buildd/subversion-1.0.9/build-tree/subversion-1.0.9/subversion/tests/libsvn_repos/run-repos-tests.py", line 11, in ?
    import exectest
ImportError: No module named exectest
END: run-repos-tests.py

Unless someone removed exectest.py for an instant (breaking one test)
and then put it back (to let the rest of the testsuite finish).

-David

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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 20 15:36:46 2004