Skip to content

Add support for directories in baseline_coverage_files #26349

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

fmeum
Copy link
Collaborator

@fmeum fmeum commented Jun 20, 2025

Files in baseline_coverage_files can now be tree artifacts that themselves contain coverage files. In addition, .gcov and .gcov.json.gz files can now also be provided for baseline coverage. Both is needed for support of GCC-style baseline coverage, which will be added in a follow-up PR.

Along the way, clean up CoverageOutputGenerator:

  • Don't reparse regexes for each source file.
  • Fail on "SEVERE" errors rather than continuing with arbitrarily truncated data.
  • Consistently use Path.

Work towards #5716

@fmeum fmeum force-pushed the 5716-refactor-coverage-generator branch 3 times, most recently from ec28a95 to 20a7862 Compare June 20, 2025 14:18
@orbl
Copy link

orbl commented Jun 20, 2025

Any chance you might do something about this? The warning would be a meaningful addition to a cleanup.

#26350?

@fmeum fmeum force-pushed the 5716-refactor-coverage-generator branch 4 times, most recently from 226b012 to 11a857c Compare June 21, 2025 15:17
@fmeum fmeum changed the title Clean up CoverageOutputGenerator Add support for directories in baseline_coverage_files Jun 21, 2025
* Don't reparse regexes for each source file.
* Fail on "SEVERE" errors rather than continuing with arbitarily truncated data.
* Consistently use `Path` throughout.
@fmeum fmeum force-pushed the 5716-refactor-coverage-generator branch 3 times, most recently from 0f9928d to 7b89648 Compare June 21, 2025 16:40
@fmeum fmeum force-pushed the 5716-refactor-coverage-generator branch from 7b89648 to 9a2b790 Compare June 21, 2025 16:41
@fmeum
Copy link
Collaborator Author

fmeum commented Jun 21, 2025

Any chance you might do something about this? The warning would be a meaningful addition to a cleanup.

#26350?

We would want to add this carefully as it risk being very noisy (but also useful). It's probably be better to do this in a separate PR so that it can also be rolled back independently if needed.

@fmeum fmeum requested a review from c-mita June 21, 2025 17:00
@fmeum fmeum marked this pull request as ready for review June 21, 2025 17:00
@fmeum fmeum requested a review from lberki as a code owner June 21, 2025 17:00
@github-actions github-actions bot added the awaiting-review PR is awaiting review from an assigned reviewer label Jun 21, 2025
@fmeum fmeum removed the request for review from lberki June 21, 2025 17:00
@iancha1992 iancha1992 added coverage team-Rules-CPP Issues for C++ rules labels Jun 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-review PR is awaiting review from an assigned reviewer coverage team-Rules-CPP Issues for C++ rules
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants