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

Checking cluster member count in watch_test #14285

Closed
wants to merge 1 commit into from

Conversation

tjungblu
Copy link
Contributor

The test should fail early on an insufficient cluster instead of
panicking during the test.

Fixes issue #14259.

Signed-off-by: Thomas Jungblut tjungblu@redhat.com

The test should fail early on an insufficient cluster instead of
panicking during the test.

Fixes issue etcd-io#14259.

Signed-off-by: Thomas Jungblut <tjungblu@redhat.com>
@@ -50,6 +50,10 @@ func runWatchTest(t *testing.T, f watcherTest) {
clus := integration.NewClusterV3(t, &integration.ClusterConfig{Size: 3})
defer clus.Terminate(t)

if len(clus.Members) != 3 {
Copy link

Choose a reason for hiding this comment

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

I've tried stepping through this test and there is check here
that waits for all members to be up. I think it checks for size implicitly.

Do we really need this extra check?

Copy link
Member

@ahrtr ahrtr Jul 31, 2022

Choose a reason for hiding this comment

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

Right, I don't think we should add the additional check either, unless you can provide a reasonable case in which the len(clus.Members) != 3 is true

@tjungblu tjungblu closed this Aug 1, 2022
@tjungblu tjungblu deleted the issue_14259 branch August 1, 2022 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants