-
Notifications
You must be signed in to change notification settings - Fork 39
Bump Go to 1.25.0 #196
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
base: main
Are you sure you want to change the base?
Bump Go to 1.25.0 #196
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: hwdef The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
6bc8c7f
to
199725a
Compare
@ivanvc |
Hey @hwdef, Prow (test-infra) is using the etcd-operator/tools/mod/go.mod Line 9 in e89aeb6
|
upgrade golangci-lint to v2: |
/retest |
Signed-off-by: hwdef <[email protected]>
@hwdef: 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-sigs/prow repository. I understand the commands that are listed here. |
I read the logs from the Prow job. Even though there are some warning logs, there doesn't seem to be any failed tests (looking for "FAIL"). I ran this locally by running Then, I ran the tests using I'm investigating further. |
It must be something in
Note that the warnings we're seeing in 1.25 are also present in 1.24. |
But go 1.24 won't fail the workflow. cc @ArkaSaha30 |
One of the issues is that this is only reproducible in the kubekins image using Go 1.25. Running locally |
I ran the tests for every module one by one, with the kubekins image, and I couldn't get it to fail 🤕 |
I found the issue. It wasn't very clear, but there are some log lines:
Which are the ones causing the issue. The problem was that the exit code and message weren't clear about it. Reference: golang/go#75031 The solution (and confirmed by me in the kubekins image with Related to: etcd-io/etcd#20576 |
Part of: etcd-io/etcd#20518