ci(fuzz): adopt ClusterFuzzLite for continuous fuzzing on PRs#102
Merged
Conversation
Wire the repo's native Go fuzz targets (FuzzMatchAny, FuzzSplitCSV, FuzzTruncPad) into ClusterFuzzLite, the self-hosted OSS-Fuzz variant recommended after our OSS-Fuzz onboarding PR (google/oss-fuzz#15574) was declined for project size: - .clusterfuzzlite/{project.yaml,Dockerfile,build.sh}: build the three targets as libFuzzer binaries via compile_native_go_fuzzer on gcr.io/oss-fuzz-base/base-builder-go (the go-118-fuzz-build shim is go-getted only inside the container, never in the repo go.mod). - .github/workflows/cflite_pr.yml: PR-triggered code-change fuzzing (300s, address sanitizer), action pinned by commit SHA, least-privilege permissions, path-filtered to Go/fuzz changes. - internal/match/fuzz_test.go: move from package match_test to package match - compile_native_go_fuzzer's rewrite cannot handle an external test package alongside the non-test package in the same directory. Verified locally in the real OSS-Fuzz container: all three fuzzers compile and run clean (fuzz_trunc_pad 64k+ execs/60s after the #100 fix it surfaced, match targets 1M+ execs/30s each). Closes #99 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Wire the repo's three native Go fuzz targets into ClusterFuzzLite — the self-hosted OSS-Fuzz variant Google recommended after declining our OSS-Fuzz onboarding (google/oss-fuzz#15574, "too immature… large user base").
.clusterfuzzlite/—project.yaml(language: go),Dockerfileongcr.io/oss-fuzz-base/base-builder-go:v1, andbuild.shcompilingFuzzMatchAny,FuzzSplitCSV(internal/match) andFuzzTruncPad(internal/ui) viacompile_native_go_fuzzer. Thego-118-fuzz-buildshim isgo get-ed only inside the container — the repo'sgo.modis untouched..github/workflows/cflite_pr.yml— PR-triggeredcode-changefuzzing (300s, address sanitizer), action pinned by commit SHA (884713a=v1, dereferenced from the annotated tag), top-levelcontents: read, path-filtered to Go/fuzz changes.internal/match/fuzz_test.go— moved from externalpackage match_testtopackage match: the go-118-fuzz-build rewrite turns the_test.gointo a non-test file, and an external test package then clashes with the real package in the same directory (caught in the local container build).Verification (run locally in the real OSS-Fuzz container)
compileentrypoint the action uses.fuzz_trunc_pad64k+ execs/60s, match targets 1M+ execs/30s each.makeslicepanic fixed in fix(ui): clamp column width to avoid makeslice panic on huge -width #101 within 5 seconds.ClusterFuzzLite PR fuzzingcheck on this very PR is the live end-to-end verification.Follow-ups (tracked in #99)
internal/align.normalizeStruct)dynamic_analysisjustification to cite continuous fuzzing in CICloses #99
🤖 Generated with Claude Code