-
Notifications
You must be signed in to change notification settings - Fork 551
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
SimpleCov affecting exit code of bacon #269
Comments
Same problem for Alchemy CMS: https://travis-ci.org/magiclabs/alchemy_cms/jobs/16516963#L403 When I remove SimpleCov from spec_helper then the failing test suite exits with 1. 0.8.1 and 0.8.2 both have this issue. Downgrading to 0.7.1 fixes the problem. My Gemfile: https://github.com/magiclabs/alchemy_cms/blob/master/Gemfile |
:( It assumes some of the recent changes to |
SimpleCov >= 0.8.1 has exit code issues: simplecov-ruby/simplecov#269
Ok, it's getting interesting :) With simplecov 0.7.1 it fails for Rails 4.1.0.beta1 environments. |
SimpleCov >= 0.8.1 has exit code issues: simplecov-ruby/simplecov#269
SimpleCov >= 0.8.1 has exit code issues: simplecov-ruby/simplecov#269
I have the same issue with cucumber features, I had failing features, but the build still succeeded because of Exit Code '0' |
I have also run into this problem with version 0.8.x. Downgrading to 0.7.1 fixes it. |
I went looking through some of the history of |
@jasonroelofs Thanks - I'll try and revert the exit status change |
Until bug is fixed simplecov-ruby/simplecov#269
Simply reverting that particular change did not help :( This issue is very likely the same as #281, and although that one came later, there is more activity over there, so I'll close this in favor of the other one. Please go on with the discussion there :) |
SimpleCov causes bacon to exit with a zero exit code even in case of failures/errors. The issue affects CI as failures are simply not reported and can go undetected.
The issue is present at least since version 0.8.1, but something more subtle might be going on.
As code speaks louder than words consider the following example:
coveralls
gem)The text was updated successfully, but these errors were encountered: