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

Enable coverage tracking for standalone code #29

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

fingolfin
Copy link
Member

@fingolfin fingolfin commented Apr 6, 2021

UPDATE: it turns out that --coverage is already being passed to the compiler for the relevant C files. Still, no coverage data is produced for them. Based on the logs, the problem might be that gcov / codecov can't find the C source files (they sit in a completely different path compared to the package's bin path

@fingolfin fingolfin force-pushed the mh/standalone-coverage branch 2 times, most recently from d46d052 to dde588c Compare April 6, 2021 21:54
@codecov
Copy link

codecov bot commented Apr 6, 2021

Codecov Report

Merging #29 (02db71f) into master (ac1e074) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #29   +/-   ##
=======================================
  Coverage   81.68%   81.68%           
=======================================
  Files          10       10           
  Lines         830      830           
=======================================
  Hits          678      678           
  Misses        152      152           

@fingolfin fingolfin force-pushed the mh/standalone-coverage branch from dde588c to 3119ac8 Compare April 6, 2021 22:06
@fingolfin fingolfin marked this pull request as draft April 6, 2021 22:54
@fingolfin fingolfin force-pushed the mh/standalone-coverage branch from 3119ac8 to 02db71f Compare October 10, 2022 12:25
@fingolfin
Copy link
Member Author

gcov can't find the source files. We may need to pass some options to it to help fix that

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.

1 participant