MAINT try docker for provisioning #565
Draft
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
davidmalloncares
force-pushed
the
MAINT-provision-test
branch
2 times, most recently
from
92cf86c to
0ca2742
Compare
davidmalloncares
force-pushed
the
MAINT-provision-test
branch
from
ee72519 to
715a505
Compare
davidmalloncares
force-pushed
the
MAINT-provision-test
branch
from
072be50 to
cb24b88
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.
Summary
CI tests very often fail the provisioning step when we opt to use the provisioning_service via litmus to provision VMs in GCP. To try to alleviate the load we put on that GCP service we will move the tests that can run in Docker over there.
Checklist
Changes include test coverage?
Have you updated the documentation?