-
Notifications
You must be signed in to change notification settings - Fork 111
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
Stick with go <1.19 #352
Stick with go <1.19 #352
Conversation
Thanks for your PR,
To skip the vendors CIs use one of:
|
Thanks! /lgtm |
Pull Request Test Coverage Report for Build 2882586772
💛 - Coveralls |
Thanks for your PR,
To skip the vendors CIs use one of:
|
Retitling as we set go version <1.19 |
Thanks for your PR,
To skip the vendors CIs use one of:
|
Thanks! /lgtm |
Before i LGTM. are we sure the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing my comments. CI use go 1.18.5 now https://github.com/k8snetworkplumbingwg/sriov-network-operator/runs/7895516472?check_suite_focus=true#step:2:12
I will always run latest version that is < 1.19 |
Good point. I tried understanding how And it seems to look in a local, repository-shared, cache. So it seems to be possible to get a go1.17 build in some rare case. Options: (personally, I'd go for a) |
I will prefer to go with There was a specific issue in 1.18.1 but in general we should not care what Z stream it use |
i would go with |
Thanks for your PR,
To skip the vendors CIs use one of:
|
Go 1.19 has different rules in `gofmt` and may lead to broken CI builds. Signed-off-by: Andrea Panattoni <apanatto@redhat.com>
Thanks for your PR,
To skip the vendors CIs use one of:
|
Ok, going for
|
Thanks for your PR,
To skip the vendors CIs use one of:
|
Signed-off-by: Andrea Panattoni <apanatto@redhat.com>
Thanks for your PR,
To skip the vendors CIs use one of:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @zeeke and sorry for the ping-pong :)
Using a dynamic version like '>=1.18.2' may lead to unexpected
build results, with new go tools in place.
This PR should fix errors like this, as they occur due to go 1.19