roachtest: add -c/--cluster for running a test on an existing cluster#22795
Merged
petermattis merged 2 commits intocockroachdb:masterfrom Feb 18, 2018
Merged
Conversation
Member
ea4e15a to
5462703
Compare
5462703 to
32b59df
Compare
Add `-c/--cluster` flag for running a test or tests on an existing cluster. When running on an existing cluster, the cluster is wiped before and after the test, but no attempt is made to create or destroy it. Like running a test locally, running on an existing cluster forces parallelism to 1. Fixes cockroachdb#22644 Release note: None
32b59df to
34eda2d
Compare
Scale the concurrency of the test by the number of nodes in the cluster. Release note: None
2298370 to
c448e2f
Compare
benesch
approved these changes
Feb 18, 2018
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
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.
Add
-c/--clusterflag for running a test or tests on an existingcluster. When running on an existing cluster, the cluster is wiped
before and after the test, but no attempt is made to create or destroy
it. Like running a test locally, running on an existing cluster forces
parallelism to 1.
Fixes #22644
Release note: None