Chore: Run tests using docker #309
Merged
Conversation
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
BeyondEvil
force-pushed
the
beyondevil/docker-tests
branch
10 times, most recently
from
5c1bbea to
72e09b7
Compare
BeyondEvil
force-pushed
the
beyondevil/docker-tests
branch
from
72e09b7 to
384cc83
Compare
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.
Switching away from the browser actions to running in docker.
This makes it so that local dev more closely matches CI.
Also removing Windows tests, because docker. We're so far away from OS-level things that this shouldn't be an issue. If we see issues we'll handle that with non-browser unit tests.
Also removed the python dev version as that was causing issue in the
develtestenv. The important thing is that we're testing dev versions of dependencies. Future python versions is a problem for another day.