Skip to content

Set GO111MODULE=on and use go mod vendor to fix Go 1.11/1.12 builds#118

Merged
crosbymichael merged 1 commit intocontainerd:masterfrom
estesp:go-mod-travis
Nov 14, 2019
Merged

Set GO111MODULE=on and use go mod vendor to fix Go 1.11/1.12 builds#118
crosbymichael merged 1 commit intocontainerd:masterfrom
estesp:go-mod-travis

Conversation

@estesp
Copy link
Member

@estesp estesp commented Nov 14, 2019

Signed-off-by: Phil Estes [email protected]

@codecov-io
Copy link

codecov-io commented Nov 14, 2019

Codecov Report

Merging #118 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #118   +/-   ##
=======================================
  Coverage   36.34%   36.34%           
=======================================
  Files          32       32           
  Lines        2102     2102           
=======================================
  Hits          764      764           
  Misses       1210     1210           
  Partials      128      128

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4baafdb...d0f61b7. Read the comment docs.

@estesp estesp marked this pull request as ready for review November 14, 2019 15:25
@estesp estesp changed the title Set GO111MODULE=on to fix Go 1.11/1.12 builds Set GO111MODULE=on and use go mod vendor to fix Go 1.11/1.12 builds Nov 14, 2019
@estesp
Copy link
Member Author

estesp commented Nov 14, 2019

Seems like somewhere in the past 6 days using a mix of go.mod and go get started failing for non-Go 1.13 builds. Since we have a go.mod we might as well use it--switching to go mod vendor from go get .. makes the last 3 Golang releases work properly in Travis CI.

@dqminh
Copy link
Member

dqminh commented Nov 14, 2019

LGTM

@estesp its because we put the package inside GOPATH, and go mod doesnt work prior go 1.13 because the default GO111MODULE=auto will not active go mod inside a GOPATH.

Either one of these things would have make things work:

  1. stop manually cloning some dependencies, put this outside of GOPATH, and do go get
  2. forcing it to active module support with GO111MODULE=on go get. This is probably the same as GO111MODULE=on go mod vendor here.

I do prefer 1) for go modules project nowadays.

@crosbymichael
Copy link
Member

LGTM

@crosbymichael crosbymichael merged commit d26e1b3 into containerd:master Nov 14, 2019
@estesp estesp deleted the go-mod-travis branch November 14, 2019 16:42
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.34%. Comparing base (4baafdb) to head (d0f61b7).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #118   +/-   ##
=======================================
  Coverage   36.34%   36.34%           
=======================================
  Files          32       32           
  Lines        2102     2102           
=======================================
  Hits          764      764           
  Misses       1210     1210           
  Partials      128      128           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

5 participants