-
Notifications
You must be signed in to change notification settings - Fork 15
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
Panic in csi-lib-utils CI #28
Comments
This issue is currently awaiting triage. If logtools contributors determine 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-sigs/prow repository. |
Error location: |
Since merely upgrading the Go version to 1.22 in kubernetes-csi/csi-lib-utils#167 |
We might have to bump the logcheck dependencies to a newer version to deal with Go 1.22. Just a guess, though. |
It seems that just upgrading the Go modules version doesn't resolve the issue. kubernetes-csi/csi-lib-utils#167 https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-csi_csi-lib-utils/167/pull-kubernetes-csi-csi-lib-utils/1787891931343228928 The error seems to be occurring in the following location: |
go: upgraded golang.org/x/exp v0.0.0-20230807204917-050eac23e9de => v0.0.0-20240506185415-9bf2ced13842 go: upgraded golang.org/x/mod v0.14.0 => v0.17.0 go: upgraded golang.org/x/sync v0.5.0 => v0.7.0 go: upgraded golang.org/x/tools v0.16.1 => v0.21.0 This fixes (at least for me) a crash when checking csi-lib-utils when using Kubernetes 1.30 there (kubernetes-sigs#28).
When I build logcheck v0.8.1 in the logcheck repo and run the binary against the csi-lib-tools PR, I get a crash. When I build inside the csi-lib-tools repo, I don't. Odd. Updating dependencies fixed the crash that I saw, so it seems worthwhile. It's just not clear whether it's solving the CI crash. |
A test build with my update in kubernetes-csi/csi-lib-utils#168 leads to a different weird failure:
I verified earlier that Go go1.22.2 is in the PATH both when building logcheck and when invoking it. Perhaps it is referring to the Go version in the logtools go.mod? |
I brought this up on the Gophers Slack and the feedback was that this might be a bug in Go, so I'll file an issue. I have found through experimentation that it works when I put "go 1.22.3" into the go.mod of logtools, so I'll put that into #29 even though it doesn't look like a proper fix. |
I turned out that the odd behavior in the CI came about because the installed Go was 1.21.5 ( The good news is that this manual download of the Go toolchain probably is not needed anymore. With Go in the container >= 1.21, it will download a newer release automatically as needed by the code that is being built. |
logcheck v0.8.1 panics when checking this PR: kubernetes-csi/csi-lib-utils#165
It could be related to k8s libraries bump and go.mod version bump to 1.22 in the PR.
The text was updated successfully, but these errors were encountered: