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

Fuzzing the verifier using debugging builds is inefficient #3512

Open
Alan-Jowett opened this issue May 1, 2024 · 1 comment
Open

Fuzzing the verifier using debugging builds is inefficient #3512

Alan-Jowett opened this issue May 1, 2024 · 1 comment
Assignees
Labels
blocked Blocked on another issue that must be done first optimization Affects perf but not correctness or applicability P2 tests triaged Discussed in a triage meeting
Milestone

Comments

@Alan-Jowett
Copy link
Member

The libfuzzer for the verifier is only acheiving around 3 iterations per second. With the size of the fuzzing space to be tested, this limits the amount of coverage we can acheive.

Proposal:
Create a FuzzerRelease configuration that builds with ASAN and full optimization. This will improve our overall fuzz coverage as it will complete more fuzzing during the scheduled CI/CD run.

@dthaler dthaler added optimization Affects perf but not correctness or applicability tests labels May 6, 2024
@dahavey dahavey added triaged Discussed in a triage meeting blocked Blocked on another issue that must be done first labels May 6, 2024
@dahavey dahavey added this to the 2406 milestone May 6, 2024
@dahavey dahavey added the P2 label May 6, 2024
@shankarseal shankarseal modified the milestones: 2406, 2407 May 14, 2024
@shankarseal
Copy link
Collaborator

@Alan-Jowett can you please comment on why this is blocked and move this to the backlog milestone?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Blocked on another issue that must be done first optimization Affects perf but not correctness or applicability P2 tests triaged Discussed in a triage meeting
Projects
None yet
Development

No branches or pull requests

4 participants