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
fix range copy issue #87777
fix range copy issue #87777
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. I understand the commands that are listed here. |
Welcome @dbenoit17! |
Hi @dbenoit17. Thanks for your PR. I'm waiting for a kubernetes 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/test-infra repository. |
/ok-to-test |
/retest |
1 similar comment
/retest |
/check-cla |
This should be fixed. Could you try running the cla-check again? |
/lgtm |
@BenTheElder do you mind approving this PR? |
@dbenoit17 lets see if we can fix in 1.16 and 1.17 branches as well? |
/priority important-soon |
@mkumatag: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. In response to this:
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. |
@dims can I get this into 1.18 release? this was blocking us to override one of the image repositories while running the tests. |
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 for fixing this!
for _, c := range containers { | ||
c.Image, err = imageutils.ReplaceRegistryInImageURL(c.Image) | ||
for i, c := range containers { | ||
containers[i].Image, err = imageutils.ReplaceRegistryInImageURL(c.Image) |
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.
ugh, we should really get a linter catching these.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, dbenoit17 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 |
/milestone v1.18 This is clearly a bug that needs fixing' |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
1 similar comment
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
The
patchContainerImages
function in the e2e test suite is intended to allow users to override some of the default e2e test image registries. Currently, this function is a no-op due to golang's copy semantics on ranges.This PR alters the function to mutate the range elements directly.
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
This function was located elsewhere in 1.16.
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: