Track test environment setup in redis #468
Merged
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
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.
Currently the autotester does not keep track of the status of test environment creation (mostly, installing test dependencies). In particular, a MarkUs user is able to run tests even when not all dependencies are installed, likely resulting in tests failing with some kind of "import error".
This PR introduces a new
_env_statusattribute in the Redis store for test settings to track the status of environment creation. This attribute has three possible values:setup: the environment is being set up (tests will not be run)ready: setup is complete and tests can now be runerror: there was an error during environment setup (tests will not be run)