Fix test runs #64
Merged
Fix test runs #64
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
MikeWooster
force-pushed
the
fix-test-runs
branch
from
9a35833
to
5204bd3
Compare
run tests as matrix. this will run multiple combinations of the specified deps for greater coverage. takes a little longer though. only run tests on push. it should not be needed for pr creation test that all latest deps are covered in tox file. pypi have disabled their search endpoint. I am using the outdated and uptodate endpoints to check that all latest deps are in the tox file test tenacity v 7.0 fix tenacity tests. tenacity removed the compat module, so I have pinched their code that I was using in their tests to set the retry state
MikeWooster
force-pushed
the
fix-test-runs
branch
from
bba6604
to
8e90f13
Compare
This was referenced Mar 20, 2021
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.
tox was not running tests. as identified by #63 .
The fix would be to pull the actual test runner command into the pyenv command. the lint environment's command should override it, and continue running as expected (i.e. not running any unit tests)