-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Latest introspector reports have zero runtime coverage information. #7635
Comments
Problem seems to have started around 20220421. |
This PR solved it: ossf/fuzz-introspector#238 I didn't bump because I would like to have this one fixed too (tomorrow) ossf/fuzz-introspector#232 -- although this one is only a minor ux thing If it's priority we can bump now and it should work |
Thanks! Let's bump now and then bump again tomorrow. Could we add some better testing here to make sure we don't break reports in the future? We're hoping to announce this to OSS-Fuzz users very soon and it's not a good look if this breaks frequently. |
Yes, will put this as priority |
There's no updates on the reports, however, I'm not sure the images are being updated? I just did:
|
I made this into a separate issue #7650 |
e.g.
https://oss-fuzz-introspector.storage.googleapis.com/zstd/inspector-report/20220427/fuzz_report.html
https://oss-fuzz-introspector.storage.googleapis.com/jsoncpp/inspector-report/20220427/fuzz_report.html
@DavidKorczynski @AdamKorcz did something break here?
@Navidem
The text was updated successfully, but these errors were encountered: