-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
coveralls should read any file that starts with .coverage #25
Comments
I'm not familiar with this kind of coverage files. |
I don't know what version of coverage this was, but I think this issue is stale at this point. Coverage 3.x and 4.x both create .coverage files. |
@jessamynsmith good point. Closing this. Feel free to reopen, if one provides a case when we need to parse more files than we do now. |
I think this occurs when coverage is called with the Perhaps I was missing something obvious, but I ran into this when trying to have tox locally combine coverage across multiple environments (using coverage 4.0a5), but still wanting coveralls to find them all when run on travis ci. I found though that you can achieve the same thing by removing the
Because coveralls uses coverage to find the file, as long as it's run in the same env that generates the coverage report, it will also respect the env var and find the file in a travis instance. When run locally, the coverage files will still have unique names, so can be combined later with Since this issue has so little activity, either I'm doing something wrong, or this seems to be fairly uncommon usage - either way it doesn't seem worth reopening and modifying code, but perhaps this comment will help others. |
Currently coverage generates coverage data files to .coverage.* format.
coveralls-python only reads files named .coverage.
The text was updated successfully, but these errors were encountered: