8000 Code coverage daily build cadence · Issue #13230 · google/oss-fuzz · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Code coverage daily build cadence #13230

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.

Sign up for GitHub

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

Jump to bottom
Open
nareddyt opened this issue Apr 17, 2025 · 12 comments
Open

Code coverage daily build cadence #13230

nareddyt opened this issue Apr 17, 2025 · 12 comments
8000

Comments

@nareddyt
Copy link
Contributor

Hi, how often do code coverage builds typically happen?

https://oss-fuzz-build-logs.storage.googleapis.com/index.html shows no projects have coverage builds since April 11th. It is now April 16th. Is this expected?
@zi0Black
Copy link
Contributor
zi0Black commented Apr 17, 2025 •
edited
Loading

Just opened #13231.

Previously was expected to build every day, or at least that is what I observed.

cc @jonathanmetzman @DavidKorczynski

@zi0Black zi0Black mentioned this issue Apr 17, 2025
Closed
@zi0Black
Copy link
Contributor

We are still without coverage builds 🥲

@nareddyt
Copy link
Contributor 8000 Author

@DavidKorczynski can you take a look? gateway project is trying to debug why our fuzzers show 0 code coverage, but it's difficult to reproduce locally. We're hoping re-enabling the daily coverage build will help us debug.

@DavidKorczynski
Copy link
Collaborator

@jonathanmetzman do you have ideas here? is it a similar issue to #13217 ?

@DavidKorczynski
Copy link
Collaborator

Should be fixed in: #13240

@DavidKorczynski
Copy link
Collaborator

will close once we see builds coming in

@evverx
Copy link
Contributor
evverx commented Apr 23, 2025

Looks like https://oss-fuzz.com/coverage-report/job/libfuzzer_asan_systemd/latest points to the coverage report built yesterday (on 2025-04-22) so it seems to have gotten back to normal.

The FI report at https://introspector.oss-fuzz.com/project-profile?project=systemd hasn't been updated yet though.

@jonathanmetzman
Copy link
Contributor

@DavidKorczynski Do you know what updates that page? The introspector builds have been happening: https://pantheon.corp.google.com/cloud-build/builds;region=us-central1/19766c20-439b-4881-9470-3bebb45cad76;step=8?project=oss-fuzz

@zi0Black
Copy link
Contributor

@DavidKorczynski can you take a look? gateway project is trying to debug why our fuzzers show 0 code coverage, but it's difficult to reproduce locally. We're hoping re-enabling the daily coverage build will help us debug.

We are also experiencing low coverage compared to local builds with just the initial seed corpus.

@evverx
Copy link
Contributor
evverx commented Apr 23, 2025

All the FI dashboards I've taken a look at have been updated as well. I'm not sure why the graphs are flat in some places but it's probably unrelated to this issue.

@DavidKorczynski
Copy link
Collaborator

I'm not sure why the graphs are flat in some places but it's probably unrelated to this issue.

Which graphs? it's looking good as far as I can tell?

@evverx
Copy link
Contributor
evverx commented Apr 24, 2025 •
edited
Loading

For example two fuzz targets vanished in systemd/systemd@d95818f and then they were brought back in systemd/systemd@39dd06d so I expected their graphs to reflect that but they are flat

Image

There should have been a visible drop from 2025-03-29 to 2025-04-21 probably.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@DavidKorczynski @evverx @nareddyt @zi0Black @jonathanmetzman
0