Links to incomplete fuzz-introspector reports

[evverx]

https://oss-fuzz-introspector.storage.googleapis.com/index.html seems to point to incomplete reports and I think it's confusing: #7599

[evverx]

I think it should point to the latest complete reports instead

[Navidem]

Is this only for the systemd case, or you may have other instances?
The index is to point to the latest successful fuzz introspector build, it does not have any sanity check on the generated reports. For that purpose something like #7593 (comment) is being considered.

[evverx]

elfutils: https://storage.googleapis.com/oss-fuzz-introspector/elfutils/inspector-report/20220421/fuzz_report.html and https://storage.googleapis.com/oss-fuzz-introspector/elfutils/inspector-report/20220419/fuzz_report.html

libbpf: https://storage.googleapis.com/oss-fuzz-introspector/libbpf/inspector-report/20220421/fuzz_report.html and https://storage.googleapis.com/oss-fuzz-introspector/libbpf/inspector-report/20220419/fuzz_report.html

selinux: https://storage.googleapis.com/oss-fuzz-introspector/selinux/inspector-report/20220421/fuzz_report.html and https://storage.googleapis.com/oss-fuzz-introspector/selinux/inspector-report/20220419/fuzz_report.html

[evverx]

The index is to point to the latest successful fuzz introspector build, it does not have any sanity check on the generated reports.

I think this issue can be closed then because the checks discussed in #7593 (comment) should prevent issues like that.

[DavidKorczynski]

It looks like there also was a regression, e.g. this is the elfutils report a month earlier https://storage.googleapis.com/oss-fuzz-introspector/elfutils/inspector-report/20220321/fuzz_report.html and coverage looks more accurate. Am actually working on the coverage as I'm writing so will look at that too

[evverx]

I'm still puzzled as to why no functions were covered at runtime according to the latest reports. Looks like the fuzz targets weren't run at all.

[evverx]

I'm still puzzled as to why no functions were covered at runtime according to the latest reports. Looks like the fuzz targets weren't run at all

For the record It was reported once again and fixed in #7635