-
Notifications
You must be signed in to change notification settings - Fork 437
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
feat: experimental tuple fuzzing setup #1873
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1873 +/- ##
==========================================
- Coverage 89.79% 88.48% -1.31%
==========================================
Files 316 316
Lines 7269 7269
Branches 1184 1184
==========================================
- Hits 6527 6432 -95
- Misses 479 581 +102
+ Partials 263 256 -7
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@terriko does this need any change before merging? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should definitely go with the "merge early, merge often" route for fuzzing experimentation. Sorry it took me a while to merge -- I just missed that you'd resolved the linter problem because the 3.7 stuff failed.
No description provided.