Skip to content

Conversation

@Anyitechs
Copy link
Owner

No description provided.

@Anyitechs Anyitechs force-pushed the upload-fuzz-coverage branch 3 times, most recently from dc493c2 to fdf6799 Compare October 13, 2025 00:25
@Anyitechs Anyitechs force-pushed the upload-fuzz-coverage branch 6 times, most recently from 6cd3f8f to 5edb8cf Compare October 30, 2025 15:25
Because each CI job runs on a fresh runner and can't share data
between jobs. We rely on Github Actions upload-artifact and
download-artifact to share the CI generated fuzz corpus, then
replay them in the `contrib/generate_fuzz_coverage.sh` script
to generate the coverage report.
Implements a persistent, global fuzz corpus cache.

PRs perform a "read-only" restore from the `main` cache
to seed fuzzer runs. The `main` branch performs a
"read-write" to save new findings and grow the corpus.
@Anyitechs Anyitechs force-pushed the upload-fuzz-coverage branch from 5edb8cf to 5807852 Compare October 31, 2025 17:12
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