test(fuzz): add honest runtime harnesses - #58
Merged
Conversation
rldyourmnd
force-pushed
the
test/fuzz-runtime-harnesses
branch
from
August 24, 2026 18:12
e39d924 to
39a3a2b
Compare
rldyourmnd
force-pushed
the
test/fuzz-runtime-harnesses
branch
from
August 24, 2026 18:16
39a3a2b to
fcefc99
Compare
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
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.
Closes #35 after live evidence. Adds a real Rust cargo-fuzz target and a complete official-shape C++ ClusterFuzzLite integration (
project.yaml, builder Dockerfile, build.sh, libFuzzer target). A path-scoped runtime workflow calls both published reusables with their real default execution paths and rejects evidence unless both caller jobs succeed. No skipped fuzzer, copied implementation, dry-run, or synthetic long soak; budgets are 1000 Rust runs and 60 seconds ClusterFuzzLite.