Centipede not enabled by default on ClusterFuzz #11964
Comments
kasper93
changed the title
kasper93
changed the title
|
Ok, it is indeed not enabled in ClusterFuzz. So while in this oss-fuzz repo it is tested/build by default, it likely is not propagated to final runners. |
kasper93
changed the title
kasper93
added a commit
to kasper93/oss-fuzz
that referenced
this issue
May 31, 2024
According to the documentation [1] and oss-fuzz source [2] it should be enabled by default. But in fact it is not enabled by default on the ClusterFuzz [3] and only project that explicity enable Centipede are using this engine. [1] https://google.github.io/oss-fuzz/getting-started/new-project-guide/#fuzzing_engines [2] https://github.com/google/oss-fuzz/blob/b07cc908abf97529a95a4dd9b3d152bf4f101e71/infra/build/functions/build_project.py#L47 [3] https://github.com/google/clusterfuzz/blob/22e11083b540518248d512141c45c25c7f560f2e/src/clusterfuzz/_internal/cron/project_setup.py#L204 See-Also: google#11964
kasper93
added a commit
to kasper93/oss-fuzz
that referenced
this issue
May 31, 2024
According to the documentation [1] and oss-fuzz source [2] it should be enabled by default. But in fact it is not enabled by default on the ClusterFuzz [3] and only project that explicitly enable Centipede are using this engine. [1] https://google.github.io/oss-fuzz/getting-started/new-project-guide/#fuzzing_engines [2] https://github.com/google/oss-fuzz/blob/b07cc908abf97529a95a4dd9b3d152bf4f101e71/infra/build/functions/build_project.py#L47 [3] https://github.com/google/clusterfuzz/blob/22e11083b540518248d512141c45c25c7f560f2e/src/clusterfuzz/_internal/cron/project_setup.py#L204 See-Also: google#11964
kasper93
added a commit
to kasper93/oss-fuzz
that referenced
this issue
May 31, 2024
According to the documentation [1] and oss-fuzz source [2] it should be enabled by default. But in fact it is not enabled by default on the ClusterFuzz [3] and only project that explicitly enable Centipede are using this engine. [1] https://google.github.io/oss-fuzz/getting-started/new-project-guide/#fuzzing_engines [2] https://github.com/google/oss-fuzz/blob/b07cc908abf97529a95a4dd9b3d152bf4f101e71/infra/build/functions/build_project.py#L47 [3] https://github.com/google/clusterfuzz/blob/22e11083b540518248d512141c45c25c7f560f2e/src/clusterfuzz/_internal/cron/project_setup.py#L204 See-Also: google#11964
DavidKorczynski
pushed a commit
that referenced
this issue
Jun 1, 2024
According to the documentation [1] and oss-fuzz source [2] it should be enabled by default. But in fact it is not enabled by default on the ClusterFuzz [3] and only projects that explicity enable Centipede are using this engine. [1] https://google.github.io/oss-fuzz/getting-started/new-project-guide/#fuzzing_engines [2] https://github.com/google/oss-fuzz/blob/b07cc908abf97529a95a4dd9b3d152bf4f101e71/infra/build/functions/build_project.py#L47 [3] https://github.com/google/clusterfuzz/blob/22e11083b540518248d512141c45c25c7f560f2e/src/clusterfuzz/_internal/cron/project_setup.py#L204 See-Also: #11964
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
According to the docs and this line, Centipede should be enabled by default. Yet, looking at the build logs, it is not built for projects that do not explicitly enable it.
I checked only a few projects, but let's consider the following examples:
bitcoin-core
centipede is explicitly enabled. The latest build log contains:
abseil-cpp
No
fuzzing_enginesdefined and no centipede in the latest build log.The text was updated successfully, but these errors were encountered: