This will prevent the builds from breaking when we do the upgrade.
Some of the issues I encountered were:
1. Installing no longer existing packages libstdc++-5-dev
2. Patch failing when I upgraded swift version (I think old version
doesn't work on focal).
Related: https://github.com/google/oss-fuzz/issues/6180
Right now this change is an NFC because base-builder-swift isn't
even being updated at the moment (see #6269)
When base-builder upgrades to 20.04, python wont be in and
base-builder these projects will fail unless they install it.
Until then, this change should be a noop.
Related: #6180
When we upgrade to 20.04, python wont be in base-builder and
these projects will fail unless they install it.
Until then, this change should be a noop.
Related: #6180
ninja-build is the intended package name. ninja-build isn't actually
needed for this project anyway.
ninja is not the build tool and isn't available in Ubuntu 20.04.
Removing this to prevent breakage.
Related: #6180
* [Ubuntu Upgrade] Upgrade msan parts to reflect new reality.
All dependencies must be built with MSAN by the project.
OSS-Fuzz will not be providing any instrumented libraries.
Related: https://github.com/google/oss-fuzz/issues/6180
suffix and pushing them to gcr.io/oss-fuzz-base.
This is useful for testing changes to images.
I used it to test changes I made for #6180.
This does not support msan as that image is being removed.
Also lint.
- Minor clarification about this using OSS-Fuzz's build chain. Be
consistent about calling this part OSS-Fuzz (rather than
ClusterFuzzLite), since that's what the image name says.
- Add project.yaml documentation.
- Refer to OSS-Fuzz's guide for efficient fuzzing.
Related: #6196
Removes unnecessary stuff in base-builder image to create a base-builder-new, and then adds a base-builder-swift on top of this that swift projects can use (without JVM/Go/etc fuzzing).
Recently the IF-MIB implementation on the Net-SNMP master branch became
dependent on libnl-route-3. An unfortunate side effect is that this broke
the build of the fuzz tests. Add the pkg-config package such that the
configure script can detect libnl-route-3 and reenable MIB-II and IF-MIB.
* Add Exiv2.
* Remove sanitizer flags so that OSS-Fuzz can insert its own.
* Using the fuzzer to create the seed corpus doesn't work with AFL.
* Only use libFuzzer
* Don't add files over 20KB to the corpus.
* Use ${LIB_FUZZING_ENGINE} when building the fuzz target.
The current way adds a lot of ordering assumptions, and doesn't fit too
well with parallel batch fuzzing either. Add a "upload-build" boolean action
input that can be added to "build_fuzzers" to upload latest builds
instead.
Builds are now uploaded by commit hash, rather than a fixed "latest" name.
ClusterFuzzLite's download_latest_build will check the last 3 commits and download the
first available build by git hash.
* Update fuzzers to new Atheris version
* Pin new atheris version
* Change = to ==
* Change path where Atheris fuzzers ld_preload from
* Update hypothesis fuzzer to work with new atheris
* Set version to 2.0.1
* Switch to Atheris 2.0.4
* Correct spelling of pygments_fuzzer decorator
* instrument yaml_reader
* Change to latest Atheris
* Set atheris version to 2.0.6
Evan Miller