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

Add code coverage instrumentation to CI pipeline #68

Merged
merged 5 commits into from
Dec 25, 2024
Merged

Add code coverage instrumentation to CI pipeline #68

merged 5 commits into from
Dec 25, 2024

Conversation

Notgnoshi
Copy link
Owner

Closes #67
Closes #64

@Notgnoshi Notgnoshi force-pushed the dev branch 5 times, most recently from cc1416c to 7b090cb Compare December 25, 2024 18:21
Additionally, split apart build and test CI jobs. Originally, the tests
required the binary produced by 'cargo build', but now that that's
fixed, and the tests require code coverage instrumentation (forcing a
rebuild anyways), it's better to do the build and test in parallel.
@Notgnoshi Notgnoshi merged commit b86a38a into main Dec 25, 2024
6 checks passed
@Notgnoshi Notgnoshi deleted the dev branch December 25, 2024 18:24
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.

Calculate code coverage in CI pipeline Integration tests fail unless you run cargo build before running
1 participant