Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

roachtest: use subtests where useful #25432

Closed
petermattis opened this issue May 11, 2018 · 0 comments
Closed

roachtest: use subtests where useful #25432

petermattis opened this issue May 11, 2018 · 0 comments
Assignees
Labels
C-cleanup Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.
Milestone

Comments

@petermattis
Copy link
Collaborator

#25408 added support for subtests which share a cluster. We should audit the existing set of tests for opportunities to use subtests to speed up running roachtests. For example, the clockjump tests look like they could all use the same cluster. Ditto for the clockmonotonic tests.

@petermattis petermattis added C-cleanup Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior. A-roachtest labels May 11, 2018
@petermattis petermattis added this to the 2.1 milestone May 11, 2018
@petermattis petermattis self-assigned this May 11, 2018
petermattis added a commit to petermattis/cockroach that referenced this issue May 11, 2018
petermattis added a commit to petermattis/cockroach that referenced this issue May 12, 2018
craig bot pushed a commit that referenced this issue May 14, 2018
25433: roachtest: make the clock jump and clock monotonic tests subtests r=bdarnell a=petermattis

Fixes #25432

Release note: None

Co-authored-by: Peter Mattis <[email protected]>
@craig craig bot closed this as completed in #25433 May 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-cleanup Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.
Projects
None yet
Development

No branches or pull requests

1 participant