This is a blocker.
Essentially, in both, 1.8 and 1.9 mode, once JRuby executes
core/proc/new_spec.rb, it doesn't execute anything alse AT ALL, just
Take a look:
mspec -t j core/proc/new_spec.rb core
Here, I execute that evil proc/new_spec first, and then the entire
core specs, and the results are:
1427 files, 1 example, 2 expectations.
TWO expectations only. That explains also why you don't see the
String errors when running the whole core set, because proc/new is
before the string, and essentially the string specs are not executed
And the spec in question that
breaks JRuby is:
Btw, MRI works just fine here, so it does look like JRuby's issue.