-
Notifications
You must be signed in to change notification settings - Fork 108
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 go mod failures #128
Fix go mod failures #128
Conversation
Because GOPATH was set to the current directory, all go commands would fail because: $GOPATH/go.mod exists but should not There is no need to explicitly go get anymore, go modules now take care of resolving missing deps just-in-time. Ran `go mod tidy` to "add missing and remove unused modules", then `go mod verify` to ensure that all deps have the expected content. [#165674069]
Running `make docker`, then `make test` inside the container resolves all deps correctly. Tests fail because there is no RabbitMQ node, as expected. `make ginkgo` & `make cover` are also working correctly from the runtime perspective, but fail due to missing RabbitMQ. [#165674069]
Had to revert the pipelines, merging this will fix the current failures linked in the PR description. To fix the release failures, you will need to cut another release. server-release:v3.8.x is currently pulling |
Thank you! |
Now that master is passing, are you going to tag a new release so that releases tests can pass as well? |
I just noticed that this broke the Travis build. Will have a go at fixing it. That must be the only thing that is blocking a new release, surely 😉 |
This is expected to fix:
Will ensure all pipelines pass with the fork before submitting this as a regular PR (currently a draft).