Running RubyGems tests with JRuby

jspencer78 · June 30, 2009, 10:30am

(originally posted to dev, but might be more useful on user)

Using JRuby 1.3.1 to run the RubyGems 1.3.1 test suite, I get an
exception
midway but no visible exception message. I used this to run the tests,
just
to simplify things (given the RubyGems-1_3_1-test directory contains the
RubyGems test directory). MRI and IronRuby run this to completion:

test_dir = File.expand_path “RubyGems-1_3_1-test”
$: << test_dir
Dir[“#{test_dir}/test_*.rb”].each { |f| require f }

Here’s the JRuby output:

JRuby limited openssl loaded. gem install support.
http://wiki.jruby.org/wiki/JRuby_Builtin_OpenSSL
EEE…F…F…F…EE…FF…F…E…EE.E.F…EF…EE…E…E…EE.FE.EEF…RubyString.java:3893:in
from org/jruby/RubyString$i_method_0_0$RUBYINVOKER$oct.gen:-1:in call’
from tar_header.rb:108:in file’
from DefaultMethod.java:154:in call’
from tar_reader.rb:59:in block_0$RUBY$block’
from CompiledBlock.java:102:in yield’
from RubyKernel.java:1147:in loop’
INVOKER$loop.gen:-1:in
callBlock’
from tar_reader.rb:56:in file’
from DefaultMethod.java:146:in call’
from CachingCallSite.java:101:in callIter’
from AbstractScript.java:53:in file’
from DefaultMethod.java:178:in call’
from CachingCallSite.java:171:in call’
from DynamicMethod.java:172:in call’
from CachingCallSite.java:155:in call’
from tar_input.rb:-1:in file’
from JittedMethod.java:196:in call’
from CachingCallSite.java:164:in callBlock’
from package.rb:56:in file’
from JittedMethod.java:230:in call’
from CachingCallSite.java:204:in callBlock’
from format.rb:67:in file’
from JittedMethod.java:145:in call’
from CachingCallSite.java:278:in cacheAndCall’
from CallOneArgNode.java:57:in interpret’
from InterpretedBlock.java:218:in evalBlockBody’
from Block.java:194:in yield’
from NewlineNode.java:104:in interpret’
from RescueNode.java:225:in executeBody’
ithJavaExceptions' from RescueNode.java:110:in interpret’
from NewlineNode.java:104:in interpret’
from InterpretedMethod.java:192:in call’
from CachingCallSite.java:288:in cacheAndCall’
from CachingCallSite.java:141:in callIter’
from LocalAsgnNode.java:123:in interpret’
from BlockNode.java:71:in interpret’
from DefaultMethod.java:143:in call’
from RubyObject.java:1413:in send’
KER$send.gen:-1:in
call’
from CachingCallSite.java:117:in call’
from unit.rb:-1:in ensure_1$RUBY$__ensure___0’
from JittedMethod.java:145:in call’
from CachingCallSite.java:278:in cacheAndCall’
from CallOneArgNode.java:57:in interpret’
from NewlineNode.java:104:in interpret’
from InterpretedBlock.java:218:in evalBlockBody’
from Block.java:194:in yield’
from org/jruby/RubyArray$i_method_0_0$RUBYFRAMEDINVOKER$each.gen:-1:in call’
from CachingCallSite.java:91:in call’
from NewlineNode.java:104:in interpret’
from InterpretedBlock.java:169:in yield’
from RubyArray.java:1562:in each’
NVOKER$each.gen:-1:in call' from CachingCallSite.java:268:in cacheAndCall’
from CachingCallSite.java:91:in call’
from NewlineNode.java:104:in interpret’
from InterpretedMethod.java:173:in call’
from CachingCallSite.java:278:in cacheAndCall’
from FCallOneArgNode.java:36:in interpret’
from BlockNode.java:71:in interpret’
from DefaultMethod.java:151:in call’
from CachingCallSite.java:117:in call’
from DAsgnNode.java:110:in interpret’
from BlockNode.java:71:in interpret’
from InterpretedBlock.java:206:in yield’
from BlockBody.java:78:in call’
from RubyProc.java:221:in call’
from Ruby.java:2580:in tearDown’
from Main.java:113:in run’

Is it know to work currently and I’m just overlooking something?

~Jimmy