Hi,
I noticed the same yesterday as well. This seems pretty serious, so I
took a look, and the results are rather unexpected. :)
It turned out that RSpec 1.2.9 had a bug so it was hiding JRuby java
integration spec failures! More specifically, cases where the java
native exception was thrown and the expectation was to not get any!
Bad, bad RSpec 1.2.9! :)
Here's an example (from method_spec):
lambda { @method.invoke Java.ruby_to_java(nil) }.should_not raise_error
While JRuby throws the following:
JavaMethod.java:232:in `invoke': java.lang.NullPointerException
from
org/jruby/javasupport/JavaMethod$i_method_0_0$RUBYINVOKER$invoke.gen:-1:in
`call'
from JavaMethod.java:630:in `call'
from DynamicMethod.java:186:in `call'
RSpec 1.2.9 happily reports that the test pass!!!! 8-)
There are 4 such hidden failures in our java integration spec suite
(three for method and one for glob). We need to fix those and upgrade
to 1.3.0 immediately!
Thanks,
--Vladimir
On Thu, Feb 25, 2010 at 4:20 AM, Joseph Athman <jjath...@gmail.com> wrote:
> It looks like JRuby will not build with the current version of rspec. I
> created a bug report for the problem. It looks like it runs fine with rspec
> 1.2.9, but not 1.3.0.
> http://jira.codehaus.org/browse/JRUBY-4596
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
