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?
to your account
Originally reported by Anonymous
But that's (sometimes) not true because:
It's a bit uncomfortable when you run all things locally before you commit your changes but finally fail because of such an issue. It happens to me several times.
I see following essential improvements you could do:
Thomas (mail: email@example.com)
The text was updated successfully, but these errors were encountered:
Original comment by Thomas Lehmann (Bitbucket: Carolinus, GitHub: Carolinus)
I can't say whether it's really an issue on the coverage.py, something with coveralls.io or the way I'm using the tool.
Here some insights (I hope it does help):
Sorry, something went wrong.
As of 5a70eeb5300d (bb), fail_under can be a float. Be careful using it, that coverage and coveralls don't round differently? Floats are tricky...
This was included in coverage.py v4.5, released today.
No branches or pull requests