scripts: Add explicit timeouts and record commit metadata in reports - #206
Merged
Conversation
Author
|
Addresses #205. |
erickcestari
suggested changes
Aug 12, 2026
erickcestari
left a comment
erickcestari
left a comment
Contributor
There was a problem hiding this comment.
Nice, really quick PR, and the commit hash is a great addition.
This should fix the issue I've recently opened #205.
morehouse
requested changes
Aug 28, 2026
morehouse
left a comment
morehouse
left a comment
Collaborator
There was a problem hiding this comment.
How was this tested? It broke for me on the first try.
Chand-ra
force-pushed
the
orchestrator
branch
2 times, most recently
from
September 1, 2026 17:18
bf069f9 to
3b2916e
Compare
Author
|
Rebased on top of the latest |
morehouse
requested changes
Sep 1, 2026
| "AFL_NO_UI": "1", | ||
| "AFL_NO_COLOR": "1", | ||
| "AFL_FORKSRV_INIT_TMOUT": "1800000", | ||
| "AFL_HANG_TIMEOUT": str(self.hang_timeout), |
Collaborator
There was a problem hiding this comment.
This is still the wrong env var.
Chand-ra
force-pushed
the
orchestrator
branch
from
September 1, 2026 20:59
d931b99 to
b9b6e12
Compare
added 2 commits
September 1, 2026 20:59
The IR programs take longer to execute than standard AFL++ inputs, so using the default AFL++ values causes false positive hangs and timeouts. Add explicit timeout durations to mitigate this.
…n reports For each configuration, record the latest Git commit metadata corresponding to that configuration and display it in the final report. This ensures evaluation data lineage and reproducibility.
Chand-ra
force-pushed
the
orchestrator
branch
from
September 1, 2026 20:59
b9b6e12 to
9a99b7d
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
3 participants
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.
This PR introduces two improvements to the Smite coverage-based effectiveness evaluation pipeline:
Explicit fuzzer timeouts: Add explicit execution and hang timeout parameters to the fuzzer invocation in
smite-orchestrator.py. This prevents false-positive hangs and timeouts for IR programs.Evaluation data lineage: Record the latest Git commit hash and date for each configuration worktree during campaign startup, displaying this metadata at the top of the generated evaluation reports. This ensures strict data provenance for a rigorous evaluation.