-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Build fails #97
Comments
|
This solves issue rubocop#97, the problem with String#uncolored not working due to interference from the colorize gem used by Coveralls.
I took care of it based on your description. I hope you think it's OK. I just removed the "monkey patching" and didn't add helper methods. |
Looks good. We can always improve this in the future. |
Many specs from cli_spec.rb are failing currently. See Travis-CI. This started with the introduction of the Coveralls code coverage gem.
All the failing specs fail for the same reason. A colored text is uncolored, which doesn't work, and then compared to an expected string without ANSI escape sequences. The comparison fails.
First I thought that the reason was that Coveralls and RuboCop both use ANSI coloring, but that they use different gems to achieve this. I tried changing RuboCop to use
colorize
(used by Coveralls) instead ofterm-ansicolor
. That didn't help one bit.Since it's the calls to
String#uncolored
that don't work, we could remove them and colorize all the expected strings instead. This fails to address the root cause, but it works. Should I implement this solution, or can anybody else find a better, more thorough solution?The text was updated successfully, but these errors were encountered: