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

Fix the build: Run integration tests with golang 1.18, ginkgo v2.1.4, and gomega v1.19 #70

Merged
merged 5 commits into from
Nov 4, 2022

Conversation

jkneubuh
Copy link
Contributor

@jkneubuh jkneubuh commented Nov 4, 2022

The recent ginkgo update requires golang 1.18. This PR fixes the build pipeline, which was pinning the test version to 1.17.

Signed-off-by: Josh Kneubuhl [email protected]

@jkneubuh jkneubuh enabled auto-merge (rebase) November 4, 2022 13:11
@jkneubuh jkneubuh changed the title run unit and integration tests with golang 1.18. Fix the build: Run integration tests with golang 1.18, ginkgo v2.1.4, and gomega v1.19 Nov 4, 2022
@jkneubuh
Copy link
Contributor Author

jkneubuh commented Nov 4, 2022

This is / was a real mess.

running go get github.com/onsi/gomega/... was forcing an upgrade to a logging package shared by controller-gen, fabric-operator, and ginkgo v2. This caused the build to break when running with golang 1.18.

With this PR, the integration tests now run with golang 1.18. The ginkgo binary installs at the latest v2.1.4, but using the older gomega v1.19.0 as specified in the go.mod.

PR #64 needs some work to sort out all of the dependencies - it forces an update of controller-gen, fabric-ca, and logging, which are all intertwined with some odd relationship based on code that may or may not be in the latest 1.5 CA.

@jkneubuh jkneubuh merged commit 4bbf88f into hyperledger-labs:main Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants