-
Notifications
You must be signed in to change notification settings - Fork 71
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
Make reporting coverage optional #274
Comments
@rski does |
@rnelson0 it still generates a coverage output. |
@rski From that screenshot, the biggest problem seems to be simplecov including vendor gems. Are you running bundle install in a particular way to get If that isn't enough, we can add |
Run
Add
It doesn't stop the coverage report entirely, but I believe addresses the main issue which is junk data. @rski comments? |
Yup, cool. This needs to be fixed in the modulesync_config or? |
yep |
Dang, I was working off an earlier version of modulesync. Here's what happens if I add it to the current setup:
I still think that's better. |
Ah right ok I was working on an earlier msync as well. So we just need to msync puppet-network, cool. |
I don't really care about having coverage reports when I'm just trying to get a test working. It might be nice to be able to disable coverage by setting an environment variable like
NO_COVERAGE_REPORT
to true or something like that.The text was updated successfully, but these errors were encountered: