[release/1.2 backport] update Go 1.12 and travis/appveyor changes#3342
Conversation
Signed-off-by: Michael Crosby <[email protected]> (cherry picked from commit 5e84069) Signed-off-by: Sebastiaan van Stijn <[email protected]>
Signed-off-by: Sebastiaan van Stijn <[email protected]> (cherry picked from commit 00bc2f5) Signed-off-by: Sebastiaan van Stijn <[email protected]>
Pervent travis from timing out because no output was printed;
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit 543d1e8)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
| GOPATH: C:\gopath | ||
| CGO_ENABLED: 1 | ||
| matrix: | ||
| - GO_VERSION: 1.11 |
There was a problem hiding this comment.
If we want to test both against 1.11 and 1.12, I can add this one back
This comment has been minimized.
This comment has been minimized.
|
@Random-Liu @jhowardmsft pls check if the commits I excluded are not needed (didn't think they were, but double-checking) |
Codecov Report
@@ Coverage Diff @@
## release/1.2 #3342 +/- ##
============================================
Coverage 43.81% 43.81%
============================================
Files 101 101
Lines 10780 10780
============================================
Hits 4723 4723
Misses 5321 5321
Partials 736 736
Continue to review full report at Codecov.
|
|
LGTM |
|
the 1.12.6 bump was merged on master; adding that one |
go1.12.6 (released 2019/06/11) includes fixes to the compiler, the linker, the go command, and the crypto/x509, net/http, and os packages. See the Go 1.12.6 milestone on the issue tracker for details: https://github.com/golang/go/issues?q=milestone%3AGo1.12.6 full diff: golang/go@go1.12.5...go1.12.6 Signed-off-by: Sebastiaan van Stijn <[email protected]> (cherry picked from commit 67cf9f7) Signed-off-by: Sebastiaan van Stijn <[email protected]>
|
Added 👍 |
|
hi @thaJeztah , I think the backport should be fix thing, not upgrade thing. Since the v1.2.x are using 1.11 for a while, if we upgrade the go version, it maybe impact the downstream using containerd v1.2. just have concerned about this. anyway, the golang upgrade action is safety. :p |
|
Golang has a shorter support period than containerd; once Go 1.13 is released (August), Go 1.11 becomes EOL, so I think it's good to follow Go versions closely where possible |
|
Failure on Windows;
@jterry75 @jhowardmsft could that be a platform issue? (I know we've seen similar things on moby) |
|
@thaJeztah thanks! agree with you |
|
you hit #2835; known issue. I restarted AppVeyor. |
[release/1.2 backport] update Go 1.12 and travis/appveyor changes
not included
Travis;
AppVeyor;
conflicts (due to #3205 not included);
Details