[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Perl/Ruby bindings fail in trunk

From: Joe Swatosh <joe.swatosh_at_gmail.com>
Date: Wed, 12 Nov 2008 16:08:41 -0800

Hey Mark,

On Tue, Nov 11, 2008 at 1:38 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> Is anyone looking at the Perl bindings? It seems like several of the
> tests are failing and they are generally not ready for the 1.6 branch.
> Ruby binding tests are also failing, but I think I have seen emails in
> the last week or so from people looking into it. Here is the Ruby
> problem I see:
> test_operation(SvnFsTest):
> /u1/build/svn-trunk/subversion/bindings/swig/ruby/svn/util.rb:86:
> [BUG] Segmentation fault
> ruby 1.8.5 (2006-08-25) [i386-linux]
> /bin/sh: line 3: 12620 Aborted /usr/bin/ruby -I
> /u1/build/svn-trunk/subversion/bindings/swig/ruby
> /u1/build/svn-trunk/subversion/bindings/swig/ruby/test/run-test.rb
> --verbose=verbose

Is this the only Ruby binding error you are seeing? Essentially none of the
tests are running for me on Windows.

I believe it is due to the first test failing in teardown() when trying to
delete the test repository (from the error message, there appears to
still be an
open file handle to the sqlite cache). From then on, all the setup()s fail
since they can't create a test repository on top of a directory with a still
open file.

I posted a patch in progress showing how I created a "session_pool" for some
client functions (add, commit, and list)
http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=144825. I'm
not sure its a good approach, but it does get some more of the Ruby bindings
tests passing.

I'll work first on the segfault you identified above as I have time....

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-13 01:08:58 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.