Skip to content

codecov - #328

Open
sdarwin wants to merge 1 commit into
edgcpp:mainfrom
sdarwin:feature/codecov
Open

sdarwin wants to merge 1 commit into
edgcpp:mainfrom
sdarwin:feature/codecov

Conversation

@sdarwin

@sdarwin sdarwin commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator

Adds codecov.io coverage reports

@wchilders-nvidia

Copy link
Copy Markdown
Collaborator

Hm, if we're going to do this, this feels like something we should factor into the primary build and test CI rather than adding yet another CI that only runs a subset of the tested configurations of the primary build & test CI.

@codecov

codecov Bot commented Oct 20, 2026

Copy link
Copy Markdown

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment

Thanks for integrating Codecov - We've got you covered ☂️

@sdarwin

sdarwin commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator Author

factor into the primary build

Updated

@wchilders-nvidia

Copy link
Copy Markdown
Collaborator

Is there some way with gcov to collect the reports and then combine them (similar to what is done with the edgy results)? I'm a little worried about the "magic number" 4 there. We have an initiative we're working on within NVIDIA to expand the number of configs that are tested and exposed within the extensive posture to expand coverage.

@sdarwin

sdarwin commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator Author

""" Good idea. Done. Each test leg now saves a gcovr JSON report as an artifact. A single coverage job, like publish-test-results, merges all coverage-* artifacts and uploads once to Codecov. There's no count anywhere anymore, so new configs in the extensive posture are covered without touching the Codecov config. The trade-off is that Codecov no longer shows a per-config breakdown. Coverage steps are all continue-on-error, so they never affect the CI result.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants