Skip to content
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

Closed
Amulyam24 opened this issue Oct 27, 2022 · 6 comments
Closed

Bump gomega to v1.23.0 #7458

Amulyam24 opened this issue Oct 27, 2022 · 6 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@Amulyam24
Copy link
Contributor

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 with

Failed to compile e2e:

# sigs.k8s.io/cluster-api/test/framework
../../../pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/alltypes_helpers.go:173:6: too many arguments in call to Eventually
        have (func() error, []interface{})
        want (...interface{})
../../../pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/cluster_helpers.go:58:5: too many arguments in call to Eventually
        have (func() error, []interface{})
        want (...interface{})
../../../pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/cluster_helpers.go:143:5: too many arguments in call to Eventually
        have (func() (string, error), []interface{})
        want (...interface{})
../../../pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/cluster_helpers.go:175:5: too many arguments in call to Eventually
        have (func() bool, []interface{})
        want (...interface{})
../../../pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/clusterresourceset_helpers.go:129:5: too many arguments in call to Eventually
        have (func() bool, []interface{})
        want (...interface{})
...
...

This is caused due to a recent change in using Eventually in gomega v1.23.0

  • cluster-api is using gomega v1.20.1

What did you expect to happen:

Anything else you would like to add:

  1. Is there a reason why an older version of gomega is used in cluster-api?

Environment:

  • Cluster-api version: 1.2.4
  • minikube/kind version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /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]

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 27, 2022
@oscr
Copy link
Contributor

oscr commented Oct 27, 2022

/triage accepted
/assign

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 27, 2022
@oscr
Copy link
Contributor

oscr commented Oct 27, 2022

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.

@sbueringer
Copy link
Member

Yup. Bumping is fine

@oscr
Copy link
Contributor

oscr commented Nov 9, 2022

@Amulyam24 This seems to be fixed in Gomega 1.24.1. Version is now being bumped in #7523

I think this issue can be closed now

@sbueringer
Copy link
Member

Yup if you bump to v1.24.1 there shouldn't be a compatibility issue with CAPI anymore

@Amulyam24
Copy link
Contributor Author

Thanks @oscr and @sbueringer !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants