-
Notifications
You must be signed in to change notification settings - Fork 188
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
Cannot build on x86_64: not enough arguments in call to watch.NewStreamWatcher #185
Comments
It looks like you are building with Go 1.13, right? Go modules were enabled by default in that version. Our repos don't have a go.mod file and it looks like We ship a working set of dependencies in Both of this should work:
Can you test and report back? I started to convert repos over to |
Hi @pohly thanks for getting back to me!
And the second one (which is working):
Of course on the ppc64le machine I get:
Is there a way to disable trying to build a windows/ppc64le version? :D |
I assumed that you had the repo checked out at If you checked out elsewhere, then Go 1.12.x already uses modules by default. It's 1.13 which enables it also when used inside
Building Windows binaries was added in kubernetes-csi/csi-release-tools#26. @ddebroy, @msau42: what was the rationale for enabling the Windows build unconditionally? Was it for the CI? Perhaps we should reconsider what "make build" is really supposed to build, i.e. what purpose it has. |
Thanks @pohly for the clarifications. |
@pohly Yes, we do want Windows versions of the CSI binaries as part of CI. I was thinking for now, adding some logic to check if GOARCH == amd64 before the Windows build step to avoid the problem above in ppc64le. That is obviously a very short term hack. Long term, we probably need a matrix of os/arch combo like in k/k at least for the node components. Thoughts? |
kubernetes-csi/csi-release-tools#35 should address |
Is this still an issue or can we close it? Release tools were updated since the bug was reported. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Hi everyone,
I am running into a bit of a weird issue.
I have one ppc64le machine in which external-attached builds without a problem:
The client-go library is:
However the exact same make command in a x86_64 machine produces the following:
The client-go library is:
Any idea what I am doing wrong? Is it a bug?
Thanks!
The text was updated successfully, but these errors were encountered: