Skip to content

Use Go 1.15 in Evergreen #492

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

Merged
merged 1 commit into from
Aug 31, 2020
Merged

Use Go 1.15 in Evergreen #492

merged 1 commit into from
Aug 31, 2020

Conversation

divjotarora
Copy link
Contributor

I filed two separate tickets to use Go 1.15 in Evergreen and to fix vet/fmt errors for 1.15, but they're dependent on each other so I have them in one pull request. Once this is approved, we can figure out if we want to backport both or rebase/merge instead of squashing and just backport the vet/fmt fixes.

@divjotarora
Copy link
Contributor Author

@kevinAlbs @iwysiu Hold off on reviewing this for now. The test runs in Evergreen are actually failing because of inconsistent vendoring, but running go mod vendor locally doesn't show any changes, so I'm not sure what's going on. I tried running a patch against the driver's master branch, and that works fine, so it seems like it's related to the 1.15 switch in this PR.

This commit also fixes errors from "go vet" and "gofmt".

GODRIVER-1729
GODRIVER-1730
@divjotarora
Copy link
Contributor Author

@kevinAlbs @iwysiu This is ready for review now.

@divjotarora divjotarora merged commit 1aa08c5 into mongodb:master Aug 31, 2020
@divjotarora divjotarora deleted the go115 branch August 31, 2020 15:29
divjotarora pushed a commit that referenced this pull request Aug 31, 2020
This commit also fixes errors from "go vet" and "gofmt".

GODRIVER-1729
GODRIVER-1730
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.

3 participants