-
Notifications
You must be signed in to change notification settings - Fork 97
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
Retry does not work for some cases in latest rspec #72
Comments
will look into this one. Thank you! |
I encountered same behavior with aggregate_failures. When I turn off aggregate_failures, it works as expected. |
Fwiw, I was not able to reproduce this in RSpec 3.6.0. |
Reproduced this in RSpec 3.8.0. |
I can confirm that it does not work when aggregate_failures is enabled. |
My focus has moved away from Ruby, so I'm not going to get to look at this. Happy to accept any PRs and / or share maintainer responsibility if anyone else has the cycles. |
@michaelglass this was discussed here: rspec/rspec-core#2289 |
@iSarCasm were you able to monkey-patch it? can you post at least the code here? |
Bumping to ask if someone can fix this or provide alternatives. I have no retries when using |
I no longer have write access to the repo and will no longer maintain it. |
The example given in the readme does not work in rspec 3.5 :
When the expectation does not match, seems rspec does not treat it as an exception anymore. so
example.exception
will still be nil and this line will pass: https://github.com/NoRedInk/rspec-retry/blob/master/lib/rspec/retry.rb#L116However, if it's a real exception like below, the retry works at expected:
The text was updated successfully, but these errors were encountered: