-
Notifications
You must be signed in to change notification settings - Fork 4k
roachtest: simplify and deflake cleanup in clock jump test #156369
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
Conversation
Closes cockroachdb#156339. Epic: none
stevendanna
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the test run passed.
| // exactly the clock jumps, we simply stop and wipe the node (which also | ||
| // prevents the post-test assertions from complaining about a down node). | ||
| c.Wipe(ctx, c.All()) | ||
| offsetInjector.recover(ctx, c.Spec().NodeCount) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this here in case the cluster gets re-used by another roachtest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think this is just for good hygiene. I'm actually not sure, maybe the failover tests reuse the clusters between each other, too.
|
TFTR! bors r+ |
Closes #156339.
Passing test run: https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/20660221?hideTestsFromDependencies=false&hideProblemsFromDependencies=false
Epic: none