-
Notifications
You must be signed in to change notification settings - Fork 63
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
clusterfuzzlite support #87
Conversation
jmartins-ledger
commented
Jun 26, 2023
•
edited
Loading
edited
- Fixed boilerplate fuzzer
- Added clusterfuzzlite support
- PR fuzzing for address/undefined/memory sanitizers (5 minutes)
- Batch fuzzing for address/undefined/memory sanitizers + Corpus prunning + code coverage report (5 minutes, At 12:00 PM, only on Saturday)
fc8439b
to
69d23f8
Compare
@jmartins-ledger Thanks! I'm wondering, is there a way to factorize the 3 differents fuzz workflows? They looks very alike. |
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #87 +/- ##
=======================================
Coverage 80.43% 80.43%
=======================================
Files 3 3
Lines 46 46
=======================================
Hits 37 37
Misses 9 9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@xchapron-ledger I merged two of them into one, since they act like cron tasks. Right now there are 2 workflows, one for cron tasks and one for PR's. I removed the external repo dependency, the artifacts can be downloaded in the github action "menu". So each fuzzing campaign takes 5min. |
8f59129
to
50b8186
Compare