bump oss-fuzz

[DavidKorczynski]

We should bump OSS-Fuzz as a reasonbly high number of changes has happened since last bump. There was a slight change in the way post-processing unit is called, so a few minor things need change in OSS-Fuzz besides bumping the LLVM number.

@Navidem @AdamKorcz do you have anything that you would like to complete before bumping on OSS-Fuzz side?

[DavidKorczynski]

we actually dont have to update the diffs as they are mainly concerned with Python. So only very minor or no diffs are needed except for the commit bump

[Navidem]

is the only change regarding post-process for OSS-Fuzz at this line?

python3 /fuzz-introspector/post-processing/main.py report $REPORT_ARGS

[Navidem]

and this too:

python3 /fuzz-introspector/post-processing/main.py correlate --binaries_dir=$OUT/

[Navidem]

re concerns on bump, I just wanted to have the bump after the summit as I will not be available to fix potential failures on OSS-Fuzz side.

[DavidKorczynski]

I think so. All of the logic in compile_python_fuzzer is irrelevant right now, and all of the logic here

fuzz-introspector/oss_fuzz_integration/oss-fuzz-patches.diff

Lines 62 to 69 in 46fa3bb

	+ if [ "$FUZZING_LANGUAGE" = "python" ]; then
	+ echo "GOING python route"
	+ set -x
	+ REPORT_ARGS="--target_dir=$SRC/inspector"
	+ REPORT_ARGS="$REPORT_ARGS --language=python"
	+ python3 /fuzz-introspector/src/main.py report $REPORT_ARGS
	+ cp -rf $SRC/inspector $OUT/inspector
	+ else

is also irrelevant and all of the logic for enabling python to be used with fuzz introspector is irrelevant.

I would say try the changes you suggest and if https://github.com/ossf/fuzz-introspector/tree/main/oss_fuzz_integration#testing-before-bumping-oss-fuzz passes then we're good

[DavidKorczynski]

@AdamKorcz are there any UI leftovers that should be addressed before bumping on OSS-Fuzz?

[AdamKorcz]

@AdamKorcz are there any UI leftovers that should be addressed before bumping on OSS-Fuzz?

@DavidKorczynski There are the descriptions in the high-level overviews.

[Navidem]

I would say try the changes you suggest and if https://github.com/ossf/fuzz-introspector/tree/main/oss_fuzz_integration#testing-before-bumping-oss-fuzz passes then we're good

let's have #411 merged, then I can test.

[DavidKorczynski]

@DavidKorczynski There are the descriptions in the high-level overviews.

ah yes. I think this one would be quite nice to complete. I will do this today.

[DavidKorczynski]

Note that test_projects.py will fail for wuffs as wuffs build is currently failing: https://oss-fuzz-build-logs.storage.googleapis.com/log-9aaac143-2250-4fd2-b86b-61e178eae971.txt

[DavidKorczynski]

@DavidKorczynski There are the descriptions in the high-level overviews.

ah yes. I think this one would be quite nice to complete. I will do this today.

This is now done. I'm good with bumping on OSS-Fuzz now.

[Navidem]

Test for could build is remaining, I will be slow to respond for the rest of the week, attending a team summit.

[Navidem]

Done via google/oss-fuzz#8078