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] Add a workflow for the code coverage #356

Merged
merged 3 commits into from
Dec 23, 2024
Merged

[CI] Add a workflow for the code coverage #356

merged 3 commits into from
Dec 23, 2024

Conversation

amontoison
Copy link
Member

No description provided.

@codecov-commenter
Copy link

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.

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

@amontoison amontoison merged commit 20fa47f into master Dec 23, 2024
13 checks passed
@amontoison amontoison deleted the coverage branch December 23, 2024 16:18
@amontoison
Copy link
Member Author

@jfowkes @nimgould
I found how to do code coverage with Meson for Fortran code and upload the results to Codecov:
https://app.codecov.io/gh/ralna/GALAHAD

I added a badge to the README so that we can easily track its evolution.
Nick, the new workflow uses all our Fortran/C tests to determine which lines in the source code are covered or not.
Lines not covered are at greater risk of bugs (functions not tested or branches of the code that we never execute).

@AndrewLister-STFC
It might interest you to know that we can achieve this with Meson and gcovr for potentially the future "SparseHSL".

@nimgould
Copy link
Contributor

Thanks, Alexis

Of course I appreciate that the GALAHAD tests are not as thorough as the HSL ones. Partially this is a lack of person power to do this justice, and part of it is because many GALAHAD packages are solving nonlinear problems for which there are inevitably pieces of code that are added as precautions without knowing if they will, indeed can ever, be executed. I honestly don't have the energy to improve this, I want to drive GALAHAD into new areas with the time I have left, not to worry about every small detail of existing codes that a 30 year old would, but a late 60 year old probably won't.

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