Rspec not returning exit code with --drb w/o spork running

Testing RSpec
1

I am seeing a problem with running rspec (rspec 2.6.0, rspec-core
2.6.4) with --drb (our default) when spork is not running. It fails to
return a non-zero error code.

Anyone has any suggestions where I should start looking? Known bug?

Thx
dB.

dblock@dblock-magenta:~/source/Gravity/dblock$ rake gravity:test:ci
(in /home/dblock/source/Gravity/dblock)
No DRb server is running. Running in local process instead …
WARNING: Nokogiri was built against LibXML version 2.7.7, but has
dynamically loaded 2.7.8
F

Failures:

  1. artwork/:slug capybara should fail
    Failure/Error: page.should have_css(‘blah’)
    expected css “blah” to return something

    ./spec/capybara_fail.rb:15:in `block (3 levels) in <top

(required)>’

Finished in 13.23 seconds
1 example, 1 failure

Failed examples:

rspec ./spec/capybara_fail.rb:14 # artwork/:slug capybara should fail
rspec spec pid 5522 exit 0

2

It seems like the problem is in Ruby, described in

But I fail to see how I can workaround that :frowning: Any ideas?

3

Ok, sorry for the spam. I applied the same change that was done in
minitest to rspec and it seems to work. Pull request here:
RSpec fails to return a proper error code when a capybara test fails by dblock · Pull Request #410 · rspec/rspec-core · GitHub.