-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add back Ruby 2.2 support for Rails 5 #2332
Conversation
689fb88
to
5227212
Compare
@benoittgt I've temporarily suppressed our phantom error as I'd like to do a release to resolve this issue in particular |
No problem Jon. |
79b4031
to
80bdca1
Compare
cd3e4a8
to
5792824
Compare
e1bb46f
to
b705036
Compare
I am late but if you need some help on this @JonRowe |
f341683
to
93c6f8c
Compare
I've just been playing whackamole with the Travis build @benoittgt 😂 I think it'll pass now, care to re-review? |
end | ||
group.run | ||
group.run(failure_reporter) | ||
expect(failure_reporter.exceptions).to eq [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not understand why we need the FailureReporter
anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its included for future debugging, we've had this spec fail before and its really hard to see why without this pattern, I'm going to use it in other places for the same reason.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Maybe we could add a little bit of documentation on the top of file or somewhere?
* Add extra debugging tool for specs expected to pass * Add back Ruby 2.2 support for Rails 5
No description provided.