-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
fuzz-introspector should show links to build logs #7599
Comments
2022-04-21 https://oss-fuzz-build-logs.storage.googleapis.com/log-cf3cc9a7-79d8-45e6-8ce4-67419987b326.txt
2022-04-19 https://oss-fuzz-build-logs.storage.googleapis.com/log-cdd966cb-78b1-4f8b-9f9a-5a3687140576.txt
|
Looking at the size of the build logs
it appears the report at https://storage.googleapis.com/oss-fuzz-introspector/systemd/inspector-report/20220421/fuzz_report.html isn't complete and it should probably be the same as https://storage.googleapis.com/oss-fuzz-introspector/systemd/inspector-report/20220419/fuzz_report.html tomorrow. If it's the case I'm not sure why https://oss-fuzz-introspector.storage.googleapis.com/index.html points to incomplete reports like that. |
I see how having a link to the full build log can be useful for the debug/test. |
I took a look at https://storage.googleapis.com/oss-fuzz-introspector/systemd/inspector-report/20220421/fuzz_report.html and judging by
it was based on incomplete data (because systemd was most likely built without lto and gold) but I'm not sure why it's different from https://storage.googleapis.com/oss-fuzz-introspector/systemd/inspector-report/20220419/fuzz_report.html. I took a look at the latest build log and it appears the same CFLAGS were used to build those reports.
Anyway, it could be that I looked at the wrong build log or something like that so it would be great if instead of going to https://oss-fuzz-build-logs.storage.googleapis.com/index.html and guessing dates there fuzz-introspector showed links to the corresponding build logs right in the reports.
The text was updated successfully, but these errors were encountered: