I thought I'd try using rspec --bisect
to figure out which combinations of tests caused a failure, but it turns out that this doesn't work with JRuby, or at least, not when launching org.jruby.Main
via java, which is how all our automated tests are set up.
The way bisect apparently works is that it launches a child rspec process.
What actually happens is...
Stderr:
sh: uri:classloader:/META-INF/jruby.home/bin/jruby: No such file or directory
Apparently rspec tells sh
to run the command for some reason. And because the command is inside the jar, this obviously can't work. If it had executed rspec directly, that might work because rspec
is a Ruby executable and JRuby might treat that differently. (There sure is a lot of "might" in here, though.)
So what I'm wondering is, is there some quick fix I can apply here to make rspec use some other method to launch the child process? Maybe it doesn't need to launch a new process? Or maybe there is a way to tell it how to launch the child process?