-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
e2e: fix return value of WaitForPodsWithLabelRunningReady #78687
e2e: fix return value of WaitForPodsWithLabelRunningReady #78687
Conversation
/sig testing |
/priority soon Trivial one-line fix that would be nice to have in 1.15. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly 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 |
/lgtm |
Because of a := assignment, the anonymous function assigned the pod list to a local variable instead of the WaitForPodsWithLabelRunningReady return value which therefore always was nil. The correct code is an assignment with = as in WaitForPodsWithLabelScheduled.
4e80fdc
to
baef3e4
Compare
@draveness I had to rebase, please lgtm again. |
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
thanks!
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
What type of PR is this?
What this PR does / why we need it:
Because of a := assignment, the anonymous function assigned the pod
list to a local variable instead of the
WaitForPodsWithLabelRunningReady return value which therefore always
was nil.
The correct code is an assignment with = as in WaitForPodsWithLabelScheduled.
Special notes for your reviewer:
Found when using the function outside of Kubernetes. Doesn't seem to affect anything in Kubernetes itself.
Does this PR introduce a user-facing change?: