Hyrum K. Wright wrote:
> Karl Fogel wrote:
>> "Hyrum K. Wright" <hyrum_wright_at_mail.utexas.edu> writes:
>>> Oh, I totally agree, but this is more a question of logistics and not
>>> one of "let's hold the release for this one last patch". From a
>>> pragmatic point-of-view, if the actually testing and signing will be
>>> held up by some quasi-foreseeable event, we might as well postpone
>>> rolling the tarball. This has the serendipitous consequence that it
>>> gives reviewers more time, and hence more stuff gets into the release.
>>
>> I do think the Wednesday that OSCON opens is a bit close, for some of us
>> anyway :-). I'd love to see a few more days to review, but if it has to
>> be Wednesday, then Wednesday it is. The important thing is to keep the
>> release buses coming, so there'll be another one along any moment now.
>
> On a related note, I won't be rolling until the r32164 group has been
> merged, since it fixes a known test failure the python bindings. It
> seems counterproductive to roll a tarball with known test failures.
I also just finished running the ruby bindings tests, with the following result:
Loaded suite .
Started
.....................................FF.............................................................................................................................................................................
Finished in 477.69542 seconds.
1) Failure:
test_merge(SvnClientTest)
/home/hwright/dev/svn-1.5.x/subversion/bindings/swig/ruby/test/test_client.rb:1015:in
`assert_merge'
/home/hwright/dev/svn-1.5.x/subversion/bindings/swig/ruby/test/test_client.rb:1019:in
`test_merge':
<[]> expected to be != to
<[]>.
2) Failure:
test_merge_peg(SvnClientTest)
/home/hwright/dev/svn-1.5.x/subversion/bindings/swig/ruby/test/test_client.rb:1015:in
`assert_merge'
/home/hwright/dev/svn-1.5.x/subversion/bindings/swig/ruby/test/test_client.rb:1025:in
`test_merge_peg':
<[]> expected to be != to
<[]>.
212 tests, 1440 assertions, 2 failures, 0 errors
make: *** [check-swig-rb] Error 1
hwright_at_spock:~/dev/svn-1.5.x$
I don't yet know if that error exists on trunk, but could one of the Ruby folks
take a look at this?
-Hyrum
Received on 2008-07-22 18:59:53 CEST