Missing Introspector data on after successful Fuzz Introspector build

[eaubin]

Is there a way to view previous Fuzz Introspector reports?

I'd like to check out Fuzz Introspector report for systemd, but don't necessarily need the latest. The webpage says the Build status: Fuzz Introspector | succeeding: Build log, but also that it is Missing Introspector data. Some graphs are not shown as there is no Fuzz Introspector data available. Please see indexing page for the relevant build logs. . The Indexing Status has a green icon for the 'Inspector build status' and links to the same build log as the project profile page.

Is it correct that the Missing Introspector data is from a delay between the running fuzz introspector and the indexer? I spot checked a few other projects and see Missing Introspector data for apache-httpd, bluez, cairo but not bind9, cgif. [Edit] Are Fuzz Introspector reports available by default only to the project owners?

[IvanNardi]

It seems the same issue reported here: #12706

[DavidKorczynski]

We did a small hack that caused projects to seemingly succeed fuzz introspector builds when they actually dont. This is because we're pushing for making a light version that needed the build process to succeed, and the goal was to enable more features of OSS-Fuzz-gen (our LLM-based harness generator). Introspector for system doesn't work, see: https://github.com/systemd/systemd/blob/b7622cbab6cd540e825ba512d4b01365cacf1176/tools/oss-fuzz.sh#L59-L69 Hidden in the introspector build log for systemd you'll also find

Step #6 - "compile-libfuzzer-introspector-x86_64": + ORIG_PYTHONPATH=/usr/local/lib/python310.zip:/usr/local/lib/python3.10:/usr/local/lib/python3.10/lib-dynload:/usr/local/lib/python3.10/site-packages
Step #6 - "compile-libfuzzer-introspector-x86_64": + export PYTHONPATH=/usr/local/lib/python310.zip:/usr/local/lib/python3.10:/usr/local/lib/python3.10/lib-dynload:/usr/local/lib/python3.10/site-packages:/usr/lib/python3/dist-packages/
Step #6 - "compile-libfuzzer-introspector-x86_64": + PYTHONPATH=/usr/local/lib/python310.zip:/usr/local/lib/python3.10:/usr/local/lib/python3.10/lib-dynload:/usr/local/lib/python3.10/site-packages:/usr/lib/python3/dist-packages/
Step #6 - "compile-libfuzzer-introspector-x86_64": + [[ introspector == undefined ]]
Step #6 - "compile-libfuzzer-introspector-x86_64": + [[ introspector == introspector ]]
Step #6 - "compile-libfuzzer-introspector-x86_64": + exit 1
Step #6 - "compile-libfuzzer-introspector-x86_64": ********************************************************************************
Step #6 - "compile-libfuzzer-introspector-x86_64": Failed to build.
Step #6 - "compile-libfuzzer-introspector-x86_64": To reproduce, run:
Step #6 - "compile-libfuzzer-introspector-x86_64": python infra/helper.py build_image systemd
Step #6 - "compile-libfuzzer-introspector-x86_64": python infra/helper.py build_fuzzers --sanitizer introspector --engine libfuzzer --architecture x86_64 systemd
Step #6 - "compile-libfuzzer-introspector-x86_64": ********************************************************************************
Finished Step #6 - "compile-libfuzzer-introspector-x86_64"
ERROR: step exited with non-zero status: 1
Starting Step #7
Step #7: Already have image (with digest): gcr.io/cloud-builders/gsutil
Step #7: CommandException: 1 files/objects could not be removed.

but some steps follow after than anyways, which is the light introspector logic.

I'll look to reverting this hack soon to make the build page clear again. Apologies for the confusion.