feat(replay): add historical POV replay workflow#214
Merged
Conversation
Add --cache-root for replay-povs so helper and latest-project state can be reused across runs under cache-local locks. Invalidate plain OSS-Fuzz build reuse when the current projects/<name> tree changes by storing a project fingerprint in build metadata, and extend replay 0day detection to include Java exception patterns already used by POV verification.
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.
Summary
replay-povsworkflow to replay discovered POVs against the latest OSS-Fuzz project state and current harness set0day-dedup.json, with docs and regression coverage for the contractTesting
uv run pytest tests/test_replay_engine.py -vuv run ruff format crsbench/ tests/scripts/ci-tests/run-local.sh checksNotes