Skip to content

allowlist: add google/clusterfuzzlite build_fuzzers and run_fuzzers - #1309

Merged
potiuk merged 1 commit into
apache:mainfrom
LucaCappelletti94:upstream/clusterfuzzlite-allowlist
Sep 18, 2026
Merged

potiuk merged 1 commit into
apache:mainfrom
LucaCappelletti94:upstream/clusterfuzzlite-allowlist

Conversation

@LucaCappelletti94

Copy link
Copy Markdown
Contributor

apache/datafusion-sqlparser-rs#2527 adds ClusterFuzzLite, so the parser's fuzz targets run on every pull request and nightly in batch mode. Its workflows use google/clusterfuzzlite/actions/build_fuzzers and google/clusterfuzzlite/actions/run_fuzzers at 884713a6c30a92e5e8544c39945cd7cb630abcd1, the commit the v1 tag points at. Without the entry every run dies with startup_failure.

Looking forward to start fuzzing in CI sqlparser-rs

@potiuk potiuk left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

verify is green on both sub-actions.

The v1 tag dereferences to 884713a6c30a92e5e8544c39945cd7cb630abcd1, matching the hash in the diff exactly. Apache-2.0 licensed, google org, and the request is anchored to a concrete consumer (apache/datafusion-sqlparser-rs#2527).

One warning on each, not a blocker: the docker images gcr.io/oss-fuzz-base/clusterfuzzlite-build-fuzzers:v1 and gcr.io/oss-fuzz-base/clusterfuzzlite-run-fuzzers:v1 are tag-pinned rather than digest-pinned. That is how ClusterFuzzLite ships, and it is the standard soft warning for docker actions rather than something this request introduces.


Drafted-by: Claude Opus 5 (no human review before posting)

@potiuk
potiuk merged commit 6bd1c60 into apache:main Sep 18, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants