You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Mark Phippard <Ma...@softlanding.com> on 2004/09/10 14:36:49 UTC

Running tests against a remote server

Quick background for those that may not have read some of my other 
messages.  My company is working on porting Subversion to OS/400, which is 
an EBCDIC system.  We are at a point where things seem to be working 
fairly well although we occasionally stumble on a new problem.  Also, an 
important point is that we are primarily interested in this as a server 
port.  IOW, we just want to be able to host a repository on an iSeries - 
OS/400 server.

We would like to be able to start to leverage the test suite so that we 
can put it through its paces.  The problem is that the test suite itself 
adds its own complications, such as the usage of Python.  Anyone have any 
ideas for how we could run a set of tests from a Windows client that 
exercises the remote OS/400 server.  Currently, using the svn:// protocol 
only?  We are only using the fsfs repositories, and we could easily map a 
drive on the Windows client to the fsfs repository if it needed direct 
access.

Thanks

Mark






_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________

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

Re: Running tests against a remote server

Posted by "D.J. Heap" <dj...@shadyvale.net>.
Mark Phippard wrote:
> Quick background for those that may not have read some of my other 
> messages.  My company is working on porting Subversion to OS/400, which is 
> an EBCDIC system.  We are at a point where things seem to be working 
> fairly well although we occasionally stumble on a new problem.  Also, an 
> important point is that we are primarily interested in this as a server 
> port.  IOW, we just want to be able to host a repository on an iSeries - 
> OS/400 server.
> 
> We would like to be able to start to leverage the test suite so that we 
> can put it through its paces.  The problem is that the test suite itself 
> adds its own complications, such as the usage of Python.  Anyone have any 
> ideas for how we could run a set of tests from a Windows client that 
> exercises the remote OS/400 server.  Currently, using the svn:// protocol 
> only?  We are only using the fsfs repositories, and we could easily map a 
> drive on the Windows client to the fsfs repository if it needed direct 
> access.
> 
> Thanks
> 
> Mark
> 
> 

I think the capability is there (mostly, at least) -- you should be able 
to build Subversion on the client and then use something like:

C:\Source\Subversion>python.exe win-tests.py -r -f fsfs -u 
svn://server-machine M:\Tests"

I haven't tried it, and it may require a bit of tweaking, but I think it 
should work or be pretty easy to make work.  The server machine would 
need to have pre-started svnserve with the root at M:\Tests where that 
is the mapped drive for the Windows client.

DJ

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