Skip to content
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

ci: report coverage #6922

Open
blueyed opened this issue Jun 2, 2019 · 1 comment
Open

ci: report coverage #6922

blueyed opened this issue Jun 2, 2019 · 1 comment

Comments

@blueyed
Copy link
Contributor

blueyed commented Jun 2, 2019

I think CI builds should report coverage (for code and tests), e.g. to codecov.io.

It might be as easy as using py-cov as a toxenv to enable it, and then upload it from there.

For performance reasons it should probably not done for all builds.

I'd be happy to provide a PR for it, but wanted to ask about / discuss it first.

@JukkaL
Copy link
Collaborator

JukkaL commented Jun 10, 2019

This would be nice if it can be implemented somehow without slowing down CI builds (e.g. if the coverage build happens asynchronously and doesn't affect build pass/fail state). We considered collecting coverage for all builds but the slowdown wasn't worth it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants