Make continuous fuzzing an option #1064
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
arcz
reviewed
Jun 2, 2023
|
Tests have to be updated too, you can run them with |
siraben
force-pushed
the
continuous-fuzzing
branch
4 times, most recently
from
ce18f0d to
d5e7bad
Compare
|
I think some tests might rely on the default test limit and they will hang now |
arcz
changed the title
samalws-tob
force-pushed
the
continuous-fuzzing
branch
from
d5e7bad to
62b10b0
Compare
|
Is there something specific stopping this from being merged? |
|
I'm not sure, but I see there's conflicts on the PR. There's also an alternative PR we could opt for here #1302 |
|
Maybe that could be merged, it'd be a nice thing to have :) |
|
@gustavo-grieco I think we should close this PR, in preference for #1302. What do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #477