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

kvserver: simplify TestClosedTimestampInactiveAfterSubsumption #65443

Conversation

andreimatei
Copy link
Contributor

Fixes #59448

This patch moves the test away from using the "old closed timestamp
mechanism" to using the new one. The test becomes simpler in the
process, and does not appear to be flaky any more (the test was
skipped).

Release note: None

Fixes cockroachdb#59448

This patch moves the test away from using the "old closed timestamp
mechanism" to using the new one. The test becomes simpler in the
process, and does not appear to be flaky any more (the test was
skipped).

Release note: None
@andreimatei andreimatei requested a review from aayushshah15 May 19, 2021 00:11
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor

@aayushshah15 aayushshah15 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @andreimatei)


pkg/kv/kvserver/closed_timestamp_test.go, line 715 at r1 (raw file):

			// Sleep a bit and assert that the closed timestamp has not advanced while
			// we were sleeping.
			time.Sleep(time.Second)

nit: is it worth it to make this a multiple of the side transport's close interval?

Copy link
Contributor Author

@andreimatei andreimatei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moved this into #65624. Please check it out there.

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @andreimatei)


pkg/kv/kvserver/closed_timestamp_test.go, line 715 at r1 (raw file):

Previously, aayushshah15 (Aayush Shah) wrote…

nit: is it worth it to make this a multiple of the side transport's close interval?

done

@andreimatei andreimatei deleted the closedts.simplify-TestClosedTimestampInactiveAfterSubsumption branch May 24, 2021 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

kv/kvserver: TestClosedTimestampInactiveAfterSubsumption failed [old closedts]
3 participants