All sounds great to me :) - Charlie (mobile)
On Apr 25, 2011, at 18:49, Erik Hollensbe <e...@hollensbe.org> wrote: > (Sorry for the top post) > > This sounds about like what I found; I'll be happy to correct these in > rubygems proper, or at least remove them from testing under RUBY_PLATFORM =~ > /java/. > > I definitely want to see what the fetcher issues are independently, they also > fail in rubinius which makes me suspect some assumption that exists in MRI > that isn't available elsewhere. > > Does anyone object to this? > > -Erik > > On Apr 25, 2011, at 3:50 PM, Charles Oliver Nutter wrote: > >> On Mon, Apr 25, 2011 at 2:30 PM, Charles Oliver Nutter >> <head...@headius.com> wrote: >>> I'd love to see JRuby have a regular CI test run against RubyGems. I >>> believe we've managed in the past to have it almost 100% green, with >>> just a few obscure failures. It definitely requires having >>> jruby-openssl installed, as you'd expect, but I think a couple of us >>> have spent time on the tests in the past. >> >> Here's a run on my system with RubyGems 1.7.1 tag and JRuby master >> (mostly 1.6.1ish). >> >> https://gist.github.com/941050 >> >> Eleven F/E total for me... >> >> * Three seem to be SSL key issues. >> >> * Four look like this, and while I remember investigating before I >> obviously didn't find the problem: >> >> 3) Error: >> test_install_domain_both_no_network(TestGemDependencyInstaller): >> Gem::RemoteFetcher::FetchError: no data for >> http://gems.example.com/gems/a-1.gem >> (http://gems.example.com/gems/a-1.gem) >> >> * A few were checking the output of building an extension. JRuby warns >> when building extensions since that support is mostly experimental, so >> it didn't match without manual patching locally. The test should be >> fixed (see gist history to see it with the original errors in place). >> >> * A couple more appear to be subtle differences in the errors we >> report for some error conditions. >> >> The pkey failures are probably the biggest concern, but overall the >> suite is pretty close to green. >> >> - Charlie >> _______________________________________________ >> Rubygems-developers mailing list >> http://rubyforge.org/projects/rubygems >> Rubygems-developers@rubyforge.org >> http://rubyforge.org/mailman/listinfo/rubygems-developers > > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
