Print what is being testing during tests and timing #308
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.
The test on TravisCI have been timing out lately; due to lack of output.
I think it is because Travis is being super-slow.
but as we get more tests the possibility for it to go over 10 minutes without output increases.
We previously added
print(" ")
between testsets to stop this.This PR goes further and just adds a print per
include
.This is also nice for testing locally, as it gives a sense of progress.
Beyond this this PR also prints timing info so we can see which tests are taking longest.
And can catch them before any get to 10 minutes.
This is what the output looks like