Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reversion Metrics #431

Open
bsamuels453 opened this issue Aug 8, 2024 · 2 comments · May be fixed by #466
Open

Reversion Metrics #431

bsamuels453 opened this issue Aug 8, 2024 · 2 comments · May be fixed by #466
Assignees
Milestone

Comments

@bsamuels453
Copy link
Contributor

For each function called by a fuzz worker, record whether the call succeeded or reverted. If it reverted, keep track of the revert reason for metrics.

At the end of a fuzz run, count up the total number of calls/reverts/revert reasons for each function and display them to the user in some way.

Stretch goal: allow the fuzzer to compare the previous run's reversion metrics to the results of the current run. This would allow detecting big issues in the harness or give dopamine hits for improving the harness.

@0xalpharush
Copy link
Contributor

#278

@bsamuels453
Copy link
Contributor Author

take

@bsamuels453 bsamuels453 self-assigned this Aug 27, 2024
@bsamuels453 bsamuels453 added low-priority planning This issue is currently in a planning/discussion phase and should not be implemented yet. labels Aug 27, 2024
@anishnaik anishnaik added this to the Version 1.1.0 milestone Feb 2, 2025
@anishnaik anishnaik added high-priority and removed planning This issue is currently in a planning/discussion phase and should not be implemented yet. low-priority labels Feb 2, 2025
@anishnaik anishnaik linked a pull request Feb 2, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants