-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Bump gomega to v1.23.0 #7458
Comments
/triage accepted |
Gomega v1.20.1 is two months old so I think it's just a case of not being updated yet. But I have created a pr to upgrade Ginkgo and Gomega. |
Yup. Bumping is fine |
@Amulyam24 This seems to be fixed in Gomega I think this issue can be closed now |
Yup if you bump to v1.24.1 there shouldn't be a compatibility issue with CAPI anymore |
Thanks @oscr and @sbueringer ! |
What steps did you take and what happened:
On bumping gomega version to 1.23.0 in
cluster-api-provider-ibmcloud
, the e2e tests(using capi test framework) fail withThis is caused due to a recent change in using
Eventually
in gomega v1.23.0What did you expect to happen:
Anything else you would like to add:
cluster-api
?Environment:
kubectl version
):/etc/os-release
):/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: