Improved patch files for failing examples #3659
Merged
Conversation
This file contains 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
Zac-HD
added
bug
Zac-HD
force-pushed
the
patching-hooks
branch
5 times, most recently
from
6704da1
to
d79d54f
Compare
Zac-HD
force-pushed
the
patching-hooks
branch
3 times, most recently
from
e7d49e7
to
6aba054
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bugfixes and enhancements following #3631, along with the remaining features for Zac-HD/hypofuzz#13 downstream 😁
Notably we now detect and handle modules that just
import hypothesisby writing@hypothesis.example(...)(CPython, you're welcome), have the ability to remove obsolete examples with known.via(...)tags (the core motivation for that method!), and skip the timestamp when computing the file hash, so that we write otherwise-identical patches to the same location instead of exploding the directory with repeated runs.