-
Notifications
You must be signed in to change notification settings - Fork 4.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
Fix upup/tools/generators/pkg/codegen staticcheck failures #8203
Fix upup/tools/generators/pkg/codegen staticcheck failures #8203
Conversation
Hi @johngmyers. 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 |
/lgtm |
/cc @rifelpet |
/retest |
Is Prow running those jobs with Go 1.11? I believe our minimum requirement is Go 1.12. |
interesting, you're right. That repo has a tool that automatically bumps image tags as they get periodically rebuilt but it seems the image we're using hasn't been updated since January so there is probably a better image we should be using. I'll do some investigation. |
The old image has not been updated in almost a year [0] and is still running Go 1.11: ``` docker run --entrypoint=/usr/local/go/bin/go gcr.io/k8s-testimages/gcloud-in-go:v20190125-cc5d6ecff3 version go version go1.11.5 linux/amd64 ``` We have open PRs [1] which are not compatible with go 1.11 which is causing their presubmits to fail. This switches those jobs to use the same kubekins image as the E2E jobs. I see other projects using the same kubekins-e2e image for non-e2e jobs as well [2]. The new image has Go 1.13 as we expect: ``` docker run --entrypoint=/usr/local/go/bin/go gcr.io/k8s-testimages/kubekins-e2e:v20191219-72db7a6-experimental version go version go1.13.4 linux/amd64 ``` [0] https://console.cloud.google.com/gcr/images/k8s-testimages/GLOBAL/gcloud-in-go?gcrImageListsize=30 [1] kubernetes/kops#8203 [2] https://github.com/kubernetes/test-infra/blob/c628c3674eb0c9292812d760232afcdbb7c79c99/config/jobs/kubernetes-sigs/cluster-api-provider-aws/cluster-api-provider-aws-presubmits.yaml#L23
The old image has not been updated in almost a year [0] and is still running Go 1.11: ``` docker run --entrypoint=/usr/local/go/bin/go gcr.io/k8s-testimages/gcloud-in-go:v20190125-cc5d6ecff3 version go version go1.11.5 linux/amd64 ``` We have open PRs [1] which are not compatible with go 1.11 which is causing their presubmits to fail. This switches those jobs to use the same kubekins image as the E2E jobs. I see other projects using the same kubekins-e2e image for non-e2e jobs as well [2]. The new image has Go 1.13 as we expect: ``` docker run --entrypoint=/usr/local/go/bin/go gcr.io/k8s-testimages/kubekins-e2e:v20191219-72db7a6-experimental version go version go1.13.4 linux/amd64 ``` [0] https://console.cloud.google.com/gcr/images/k8s-testimages/GLOBAL/gcloud-in-go?gcrImageListsize=30 [1] kubernetes/kops#8203 [2] https://github.com/kubernetes/test-infra/blob/c628c3674eb0c9292812d760232afcdbb7c79c99/config/jobs/kubernetes-sigs/cluster-api-provider-aws/cluster-api-provider-aws-presubmits.yaml#L23
FWIW i ran the generator using both the master branch and this branch and the output was identical, so hopefully kubernetes/test-infra#15691 will get merged soon |
/retest |
There we go! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johngmyers, rifelpet 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 |
@johngmyers: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
Ref:#7800