On 2005-06-18 12:23-0400, David James wrote:
> Jani's Test Box wrote:
...
> FYI, I get this same error whenever the test suite tries to use a port
> that is already in use by my firewall. Now that Kouhei has switched
> the port in r15077, the test suite works fine on my system. I don't
> know what's causing Jani's problem here.
I will give it a look at some point.
>
> For more debugging information, see
> http://subversion.tigris.org/servlets/ReadMsg?list=svn-breakage&msgNo=30609
>
> Jani's Test Box wrote:
> > /srv/svntest/svntest/svn/svn_trunk/ac-helpers/install-sh -c -d
> > /usr/lib/ruby/site_ruby/1.8/x86_64-linux/svn/ext
> > mkdir: cannot create directory `/usr/lib/ruby/site_ruby/1.8/x86_64-linux/svn': Permission denied
> > mkdir: cannot create directory `/usr/lib/ruby/site_ruby/1.8/x86_64-linux/svn/ext': No such > file or directory
> This problem is caused by the fact that the test suite does not have
> access to the Ruby installation dir, so we cannot test whether the
> installation process works.
Yep. I am running test suite without installing it first, isn't there
a bug in ruby's make system, when it tries to install something even
when it has been called without "install"?
The case is similar with perl unit tests which have to be called with only
following "swig-pl" "" "check-swig-pl" targets.
I am running the ruby test suite with following targets at the moment:
"swig-rb" "" "check-swig-rb".
> Jani, can you install Ruby in a local dir where the test suite will
> have access?
I am sorry, but I won't do that. The system is running under chroot
jail, so in theory I could do what ever with it, but to get reliable
test results I think it is better if things get installed under
recyclable locations which could be erased before a new test round.
BR, Jani
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 19 00:15:26 2005