[release/1.6] Build binaries with 1.21.1#9180
Conversation
1.19 is end of life, continue to run with 1.20 but ensure builds with 1.21. Signed-off-by: Derek McGowan <[email protected]> (cherry-picked from 4ffa3ed) Signed-off-by: Kern Walster <[email protected]>
|
Hi @Kern--. Thanks for your PR. I'm waiting for a containerd 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. DetailsInstructions 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. |
|
The Vagrant error seems unrelated: |
Yes, this is new and not a flake as I restarted to see if this was some temporal issue with VBox. I don't think we've ever seen this before; need to investigate so we can get |
|
Also curious why the other 2 vagrant-centric CI jobs did not fail with this error when they all use the same core vagrant script/config? Any ideas @AkihiroSuda? |
|
It looks like this PR only updated 1 of the files to go1.21.3, but all other files continue to test against go1.20.8; was that intentional? |
go 1.19 is EOL and doesn't work well with windows-2019 in CI.
Cherry-pick from #9167
This should fix the windows-2019 failures.