Reduce logged pytest output #621
Open
+8
−8
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
tommbendall
added
tidying
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.
This PR attempts to reduce the amount of output from our pytest runs.
Currently, for failing tests, pytest will print (to terminal) our logged messages not once but twice. As the default log level is
DEBUG, this actually can make it hard to find the traceback from failed tests.As we already store (and upload in our CI) the Gusto logs which contain all of the log calls, I think it might be more helpful just to suppress pytest from printing whatever Gusto logs.
I think the simplest way to do this is by adding
--show-capture=noto pytest calls.