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

Update coverage stats. #714

Merged
merged 1 commit into from
Nov 10, 2024
Merged

Update coverage stats. #714

merged 1 commit into from
Nov 10, 2024

Conversation

oliverchang
Copy link
Collaborator

They were very very out of date.

They were very very out of date.
@oliverchang oliverchang merged commit 2971f03 into main Nov 10, 2024
4 of 5 checks passed
@oliverchang oliverchang deleted the update-readme-cov branch November 10, 2024 08:32
\* "Total coverage gain" is calculated using a denominator of the total lines
of source code compiled during the OSS-Fuzz build process for the entire
project. "Total relative gain" is the increase in coverage compared to the old
number of covered lines.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better to explain that some unintuitive high percentage (e.g., 98%) may due to more code are included while compiling the new fuzz target? E.g.,
"Some high percentage gains result from additional code included while compiling the new fuzz targets."

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! Can you please raise a PR to add this explanation?

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.

2 participants