* apache-httpd: initial integration with PoC fuzzers.
* updated project with apache emails and added more fuzzing. More to come
* use trunks of apache projects.
* fix build.
* updated build to enable pool debugging.
Don't assume that path is relative to workspace if it is not absolute.
Only make this assumption on GitHub where it will always be true.
Also, add tests.
This should mostly complete support for affected fuzzers for external users.
This implementation is still imperfect however.
It relies on the name of the repo being the same as the name of the directory in $SRC/ that the repo is checked out in
(i.e. repo must be checked out in $SRC/$REPO_NAME).
While installing `libxext-dev` in `base-runner` makes it available for local fuzzing via `infra/helper.py run_fuzzer`, it is not installed in the image used by ClusterFuzz to run fuzz targets. Fuzz targets that rely on any JDK system dependency rather have to install it manually using the method described in https://google.github.io/oss-fuzz/further-reading/fuzzer-environment/#runtime-dependencies.
By removing this package from `base-runner`, a failure to do so will already be detected via a local `check_build` rather than only during fuzzer execution on ClusterFuzz.
- Add storage-repo, storage-repo-branch, and
storage-repo-branch-coverage fields to the actions, to indicate that
the Git filestore should be used.
- The CI provided filestore is still used for crashes and builds.
- Replace generic Filestore.upload_directory with typed upload methods
which matches the download methods.
- Rename upload_latest_build to upload_build to make it more generic.
- Make artifact name prefixes an implementation detail of the store.
For #6052.
* [net-snmp] Include <unistd.h> for getpid()
* [net-snmp] Split and improve snmp_octet_fuzzer
Split snmp_octet_fuzzer into one fuzzer per function to make bug reports
easier to interpret. See also commit ded8766460 ("net-snmp: add two new
fuzzers and simplify build script. (#6091)")
Running the fuzzers in headless mode works around missing dependencies
for the full Java AWT libraries. It is likely that the commons-imaging
only uses features available in headless mode, in which case this would
be a complete fix for the fuzzer startup crashes observed on
ClusterFuzz.
This can be useful for artifacts we want to upload that we know
do not need to be tarred, such as crashes. It's important not
to tar these because they will need to be viewed by users.
Previously, the downloaded build was uploaded instead of the new build.
This regression was introduced when the big workspace change was made.
Also, add more logging.
Jean-Michel Picod