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
Feature/issue 350 #360
Feature/issue 350 #360
Conversation
Codecov Report
@@ Coverage Diff @@
## master #360 +/- ##
=======================================
Coverage 82.49% 82.49%
=======================================
Files 39 39
Lines 7850 7850
=======================================
Hits 6476 6476
Misses 1374 1374 Continue to review full report at Codecov.
|
travis-fuzz isnt whats used to generate the fuzz outputs, though it may be useful to have a contrib/rename-fuzz-files.sh file that can be installed as a git pre-commit hook. |
@TheBlueMatt I know. The idea was that travis-fuzz.sh would reveal that newly added/modified fuzz inputs will cause trouble for Windows users. I'm open to make changes. |
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.
Oops, I'm sorry, I didn't read close enough. Looks good.
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.
lgtm
Tested on Windows, using: