On Wed, Dec 23, 2009 at 09:35:23AM -0600, Hyrum K. Wright wrote:
> Please be sure to test the bindings.
Also, a ruby bindings test segfaults.
I've found this in an OpenBSD ports build, hence no debug symbols
in this trace. I can rebuild it with debug symbols if required.
#0 0x007f64b5 in kill () from /usr/lib/libc.so.53.0
#1 0x0084365b in abort () at /usr/src/lib/libc/stdlib/abort.c:68
#2 0x049a0e22 in rb_bug () from /usr/local/lib/libruby.so.2.0
#3 0x049ff537 in sigsegv () from /usr/local/lib/libruby.so.2.0
#4 <signal handler called>
#5 0x074077ec in svn_path_join () from /usr/local/lib/libsvn_subr-1.so.1.2
#6 0x04ce68cd in resolve_conflict_on_entry ()
#7 0x04ce6d6b in resolve_found_entry_callback ()
#8 0x04cf17ee in visit_tc_too_found_entry ()
#9 0x04cf1474 in walker_helper () from /usr/local/lib/libsvn_wc-1.so.1.2
#10 0x04cf175d in svn_wc_walk_entries3 ()
#11 0x04cf1ab7 in svn_wc__walk_entries_and_tc ()
#12 0x04ce6ffc in svn_wc_resolved_conflict4 ()
#13 0x09a4bcdb in svn_client_resolve ()
#14 0x02ab5f6d in _wrap_svn_client_resolve ()
We have not had a release in a while with no bindings test failures.
Should we practice self-discipline by not allowing ourselves to release
1.6.7 with test failures in the bindings?
By the way, the ruby bindings tests don't run in a 1.6.x working copy
checked out with a trunk client :(
Almost every test fails as follows:
Svn::Error::WcUnsupportedFormat: subversion/libsvn_wc/questions.c:65: Svn::Error
::WcUnsupportedFormat: The path 'wc-tmp/wc' appears to be part of a Subversion 1
.7 or greater
working copy rooted at '/home/stsp/svn/svn-1.6.x/subversion/bindings/swig/ruby/t
This problem is easily worked around, but running tests should really
Received on 2009-12-26 20:25:05 CET