Open
Conversation
(Instead of gunicorn)
With coverage we run with the flask dev server, which keeps state across requests. Errors causes by relying on the state are more likely to be caught by gunicorn
Contributor
|
Leaving this one in the capable hands of @kprimerakis. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Print a coverage report at the end of
make check. Opens the door to check for a minimum coverage, or checking that the coverage doesn't decrease.Why this? I started exploring it, seemed possible, then it was one rabbit hole after the other. Next time I'll think twice before thinking "I'll finish this just because I started it".