Caching the hypothesis db. #658
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
|
How do we know if it works? |
Excellent question. I've spoken to the maintainer of hypothesis and this is how he said to do it. Based on the travis documentation about making things persist it seems to make sense. Ultimately I don't think there is a way of knowing (even if the same failed example was triggered twice: that wouldn't necessarily confirm it)... At worst it's not working which would not actually change anything from the status quo. |
|
I guess we'll find out soon! |
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.
(I believe) this closes #595.
It caches the hypothesis failure database. It just means that travis will keep track of parts of the test space for which tests previously failed.