-
Notifications
You must be signed in to change notification settings - Fork 154
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
Coverage not working in production #404
Comments
Hmmm In develop you see runtime coverage, but in production you are just getting load time on a few files but no additional data after that? Do you happen to use scoutapp? They have a bug which breaks coverage: scoutapp/scout_apm_ruby#343 You could try turning on verbose logging in production briefly to see if any of the logged output is helpful. |
@danmayer thanks for the quick answer. Yes we use Scout and disabling |
Should I create a PR with something like "Known Issues" sections to the README pointing out that it won't work when Scout APM has |
yeah that would be great, if you want to send a PR please do, if not I will work on adding that section |
Hi, I've added the gem to our project's Gemfile and enabled the WEB UI. It seems to be working on development env, but in production it just collects this data: https://i.imgur.com/YLmFDFo.png
Everything else shows as 0%, not sure what is happening. I've tried manually starting Coverband inside an
after_initialize
hook but it doesn't make any difference.Coverband: v5.0.1
Ruby: v2.6.3
Rails: v5.2.3
Production deployed to Heroku
The text was updated successfully, but these errors were encountered: