On 3/12/06, Peter N. Lundblad <peter@famlundblad.se> wrote:
> Hi,
>
> I wanted to vote for the r17280 backport group in 1.3.x/STATUS, but got a Ruby
> test failure.
>
> I am using SWIG 1.3.28 and Ruby 1.8.4 on Debian testing.
>
> I checked out a fresh WC, merged the integration branch and ran:
> make all swig-py swig-pl swig-rb
> make check-swig-pl check-swig-py check-swig-rb
>
> The last target gave the following output:
> cd /home/pl/src/svn/13x/subversion/bindings/swig/ruby; \
> /usr/bin/ruby -I /home/pl/src/svn/13x/subversion/bindings/swig/ruby \
> /home/pl/src/svn/13x/subversion/bindings/swig/ruby/test/run-test.rb \
> --verbose=normal
> Loaded suite test
> Started
> ................................................................................................................F......
> Finished in 299.491669 seconds.
>
> 1) Failure:
> test_locked(SvnWcTest)
> [/home/pl/src/svn/13x/subversion/bindings/swig/ruby/test/test_wc.rb:333:in `test_locked'
> /home/pl/src/svn/13x/subversion/bindings/swig/ruby/test/util.rb:55:in `change_gc_status'
> /home/pl/src/svn/13x/subversion/bindings/swig/ruby/test/util.rb:70:in `gc_enable'
> /home/pl/src/svn/13x/subversion/bindings/swig/ruby/test/test_wc.rb:331:in `test_locked']:
> <false> is not true.
>
> 119 tests, 616 assertions, 1 failures, 0 errors
>
> The tests all pass using SWIG 1.3.25. Is this a known problem, or does it
> look like something that could be wrong on my system?
It is a known problem with SWIG 1.3.28 and the Ruby bindings, I have
always gotten the same error. We have not looked into what causes it.
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 13 09:03:13 2006