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 go mod failures #128

Merged
merged 3 commits into from Apr 29, 2019
Merged

Fix go mod failures #128

merged 3 commits into from Apr 29, 2019

Conversation

gerhard
Copy link
Collaborator

@gerhard gerhard commented Apr 29, 2019

This is expected to fix:

Will ensure all pipelines pass with the fork before submitting this as a regular PR (currently a draft).

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]
@gerhard
Copy link
Collaborator Author

gerhard commented Apr 29, 2019

I've just realised that I can only address master failures, since release will require you to tag a new release.

server-release:v3.8.x is now passing with these changes:
image

@gerhard
Copy link
Collaborator Author

gerhard commented Apr 29, 2019

server-release:3.7.x is passing as well:
image

@gerhard gerhard marked this pull request as ready for review April 29, 2019 11:39
@gerhard
Copy link
Collaborator Author

gerhard commented Apr 29, 2019

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 rabbit-hole release v1.6.0-rc.1. Same for server-release:v3.7.x.

@michaelklishin michaelklishin merged commit 76be1de into michaelklishin:master Apr 29, 2019
@michaelklishin michaelklishin deleted the fix-go-mod-failures branch April 29, 2019 15:36
@michaelklishin
Copy link
Owner

Thank you!

@gerhard
Copy link
Collaborator Author

gerhard commented Apr 29, 2019

Now that master is passing, are you going to tag a new release so that releases tests can pass as well?

@gerhard
Copy link
Collaborator Author

gerhard commented Apr 29, 2019

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 😉

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.

None yet

2 participants