Skip to content

Conversation

@tbg
Copy link
Member

@tbg tbg commented Oct 28, 2025

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@tbg tbg requested a review from stevendanna October 28, 2025 11:00
Copy link
Collaborator

@stevendanna stevendanna left a 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)
Copy link
Collaborator

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?

Copy link
Member Author

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.

@tbg tbg marked this pull request as ready for review October 30, 2025 09:37
@tbg tbg changed the title roachtest: simplify cleanup in clock jump test roachtest: simplify and deflake cleanup in clock jump test Oct 30, 2025
@tbg
Copy link
Member Author

tbg commented Oct 30, 2025

TFTR!

bors r+

@tbg tbg added the backport-all Flags PRs that need to be backported to all supported release branches label Oct 30, 2025
@craig
Copy link
Contributor

craig bot commented Oct 30, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-all Flags PRs that need to be backported to all supported release branches target-release-26.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

roachtest: clock/jump/large_backward_enabled failed

3 participants