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

Expose code coverage #173

Merged
merged 1 commit into from
Feb 13, 2024
Merged

Conversation

SimonRichardson
Copy link
Member

Exposes code coverage so that we can provide analysis on it later.

Exposes code coverage so that we can provide analysis on it later.
@jameinel
Copy link
Member

I'm happy for us to do this conceptually, I think it is good for us. Does this cause problems with overhead/causes borderline tests to start to fail?

Should we be targeting 3.4 for this as well?

@SimonRichardson
Copy link
Member Author

@jameinel I want to see how much it costs us first, we might have to move this somewhere else if it is expensive to run.

Copy link
Member

@jack-w-shaw jack-w-shaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we can see from runs like:
https://jenkins.juju.canonical.com/job/github-make-check-juju/11737/

Adding these coverage reports has a negligible cost

@SimonRichardson SimonRichardson merged commit 073f7a2 into juju:main Feb 13, 2024
2 checks passed
@SimonRichardson SimonRichardson deleted the expose-codecoverage branch February 13, 2024 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants