-
-
Notifications
You must be signed in to change notification settings - Fork 763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Odd output for "Caused by" #2155
Comments
That is a bit odd. The Could you provide an executable example of the problem? |
@mockdeep are you using selenium, poltergeist, or capybara-webkit or the like? |
@JonRowe Yeah, we're using capybara with selenium, though these are controller specs, which shouldn't be touched by capybara. I tried it out in another application with the same rspec version and it works as expected, so I'll see if I can narrow down the issue. It's odd because I wouldn't expect a cause to be displayed at all here, since no error was raised... |
Yes thats a sideeffect of how RSpec works, we use exceptions for test failures, and in this case the cause is displayed as it was present for some reason |
Okay, figured it out. We have Failures:
1) Admin::AdminController#ensure_admin! when the user is an admin does nothing
Failure/Error: expect(flash[:error]).not_to be_nil
expected: not nil
got: nil
# ./spec/controllers/admin/admin_controller/ensure_admin_bang_spec.rb:22:in `block (3 levels) in <module:Admin>'
# ------------------
# --- Caused by: ---
# Errno::ECONNREFUSED:
# Connection refused - connect(2) for "127.0.0.1" port 8989
# /home/fletch/.rvm/rubies/ruby-2.1.7/lib/ruby/2.1.0/drb/drb.rb:839:in `initialize' We're not using a drb server, so for now will just remove the configuration. |
Thanks for figuring out that the I figured out the problem and fixed it in #2156. |
Great, thanks! |
I'm seeing some confusing output when a spec fails after upgrading from
3.3
5o3.4
. For the most part everything is the same, but the newCaused by
section saysErrno::ECONNREFUSED
. Is there some setting I'm missing?The text was updated successfully, but these errors were encountered: