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
merge error check to validateEndpointsPorts #99146
merge error check to validateEndpointsPorts #99146
Conversation
@JornShen: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
/cc @aojea |
19f5956
to
ffa7789
Compare
I´m not thrilled with these changes, last time that someone has changed one function in the opposite order, from failing to return err, we were running tests without checks during several months and nobody noticed ... the e2e framework grew organically and there are a lot of places and dependencies that are hard to detect I'm sorry but I rather prefer to keep things the way they are unless we see a clear improvements ... the risk is too high and I can't see a big return |
It a private func and only used in service.go and conntrack.go file 
|
yeah, I understand the goal and the intention, and appreciate it ... but I can't see that the returned value is enough, also this will complicate possible backports later |
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.
Thanks!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JornShen, thockin 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 |
/retest Review the full test history for this PR. Silence the bot with an |
/kind cleanup
I found after calling the validateEndpointsPorts, tests will do the same judge(use framework.ExpectNoError).
Merge this check to validateEndpointsPorts to make it more clear.