-
Notifications
You must be signed in to change notification settings - Fork 25
fixed bug in integration test #849
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
fixed bug in integration test #849
Conversation
Hi @anshuman-agarwala. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
tests/it/utils.go
Outdated
@@ -121,15 +119,13 @@ func newCSIClient() (*CSIClient, error) { | |||
return nil, err | |||
} | |||
var conn net.Conn | |||
err = wait.PollUntilContextTimeout(context.Background(), 10*time.Second, 3*time.Minute, true, func(context.Context) (bool, error) { | |||
Eventually(func() error { |
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.
Any problem using Poll func?
We need to revert the change at line 128: return false, nil
and add err at line 127: klog.Warningf
Refer similar fix at https://github.com/kubernetes-sigs/ibm-powervs-block-csi-driver/pull/842/files
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.
There's no problem in using the poll func, my reasoning was that Eventually is doing the same thing and we don't have to explicitly ignore the timeout error, ginkgo will simply throw that if the polling time limit is exceeded. This just looks like a simpler flow to me.
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.
IMO let's stay with existing code and to make the linter happy put err in the warning msg.
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.
Done
50a88e8
to
bdb69f4
Compare
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anshuman-agarwala, yussufsh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
What type of PR is this?
/kind test
What this PR does / why we need it:
Fixes a minor bug which was causing integration tests to fail consistently.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: