-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
dropNetworking function doesn't compile when building Tekton release #3612
Comments
…package." This reverts commit e097c52. The int used `Size: 4294967295` seems to be too large for the machines that we build Tekton on! Or too large for int anyway Opened tektoncd#3612 to figure out a longer term fix but for now let's revert this to make sure we're in a releasable state.
Do you know how this ran? What cluster/task was it in? I'm trying to repro now. |
|
Thanks! It looks like this happens because we're cross compiling for 32-bit architectures. We don't currently build that in pre-submit tests. I think that would have to go somewhere in here: |
pre-submit check: build: run ko resolve on build presubmit 🙃 #3621 @bobcatfish shall we close this issue (#3612) |
@nikhil-thomas I think we should yes. |
@vdemeester: Closing this issue. 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. |
In #3582 we added a function that has this code:
Unfortunately the value for size is too big for some systems! I guess that the machines we build on must use int32 instead of int64? Not sure exactly but long story short @jerop and I tried to make a release today and when ko ran it errored with:
I'm gonna revert this for now until we can fix it, I dunno if we can just cast the value to int64 or if we need to do something to update the images we build on (maybe both)?
At the very least we should know at PR time that this kind of thing is going to fail so maybe in the long run we can invoke the same Task in our end to end tests :S
The text was updated successfully, but these errors were encountered: