Across many projects I have seen this same thing where running
limelight specs just kills the process. Then I will run it again
and sometimes it will pass and sometimes it will fail. Below is an
example of the output where running the same spec command twice in
a row without changing the code gave me different results.
(in /Users/paulwpagel/Projects/magistro) JRuby limited openssl
loaded. http://jruby.org/openssl
gem install jruby-openssl for full support.
.........Paul-Pagels-MacBook-Pro:magistro paulwpagel$ jruby -S rake
spec (in /Users/paulwpagel/Projects/magistro) JRuby limited openssl
loaded. http://jruby.org/openssl
gem install jruby-openssl for full support.
.......................FFF.....
1)
'Rspec Runner#run has an initially empty error stream' FAILED
expected: "",
got: "errors" (using ==)
./spec/lib/rspec_runner_spec.rb:28:
2)
'Rspec Runner#run has an initially empty output stream' FAILED
expected: "",
got: "output" (using ==)
./spec/lib/rspec_runner_spec.rb:32:
3)
NoMethodError in 'Rspec Runner#run has initial
examples_should_be_run'
undefined method run_examples' for
#<RspecRunner:0x321df5c7><br/>
./spec/lib/rspec_runner_spec.rb:36:
Finished in 2.792 seconds
31 examples, 3 failures