Skip to content

fix: avoid collisions between FuzzRemoveRules fuzzers#1386

Merged
egibs merged 1 commit into
chainguard-dev:mainfrom
egibs:fix-fuzzer-collisions
Feb 18, 2026
Merged

fix: avoid collisions between FuzzRemoveRules fuzzers#1386
egibs merged 1 commit into
chainguard-dev:mainfrom
egibs:fix-fuzzer-collisions

Conversation

@egibs
Copy link
Copy Markdown
Member

@egibs egibs commented Feb 18, 2026

Addresses:

Run go test -parallel=1 -timeout 0 -fuzz="FuzzRemoveRules" -fuzztime="${FUZZ_TIME}" "./pkg/compile/"
testing: will not fuzz, -fuzz matches more than one fuzz test: [FuzzRemoveRules FuzzRemoveRulesRegex]
FAIL
exit status 1
FAIL	github.com/chainguard-dev/malcontent/pkg/compile	57.211s
Error: Process completed with exit code 1.

FuzzRemoveRulesRegex worked because it was a unique test but this failed because it matched more than one fuzzer. This PR updates the name to be unique and avoids future collisions by anchoring future patterns like we do in the Makefile.

Signed-off-by: egibs <20933572+egibs@users.noreply.github.com>
@egibs egibs requested a review from stevebeattie February 18, 2026 13:41
@egibs egibs enabled auto-merge (squash) February 18, 2026 13:53
Copy link
Copy Markdown
Member

@stevebeattie stevebeattie left a comment

Choose a reason for hiding this comment

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

Nice fix, thanks!

@egibs egibs merged commit 544be5a into chainguard-dev:main Feb 18, 2026
18 checks passed
@egibs egibs deleted the fix-fuzzer-collisions branch February 21, 2026 16:24
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