Conversation
|
Golang update looks to be fixing issues on s390x |
|
Wait; why are all builds failing? |
|
Kicked CI to see if it was a temporary issue with GitHub |
|
Nope; looks like an actual regression? Wondering if it's an issue in the image, or golang |
|
So... I just saw gotestyourself/gotestsum#110 Is go modules somehow looking for the go modules from "master" instead of the version we checked out??? |
|
OK, so this fails on Go 1.13.10 as well. What happens is; First, we Which gets the latest version from master, and fetches the dependencies used on master Then we checkout the that fails, because master no longer depends on logrus (so the initial |
00d09f7 to
122ead6
Compare
|
moved to draft, waiting for #40979 to be merged |
e36d7f4 to
993a175
Compare
full diff: golang/go@go1.13.10...go1.13.11 go1.13.11 (released 2020/05/14) includes fixes to the compiler. See the Go 1.13.11 milestone on the issue tracker for details: https://github.com/golang/go/issues?q=milestone%3AGo1.13.11+label%3ACherryPickApproved Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
993a175 to
90758fb
Compare
|
Looks like ppc64le images are missing; build status: https://doi-janky.infosiftr.net/job/multiarch/job/ppc64le/job/golang/. Some previous builds failed because the node was out of disk space; perhaps that's the problem? /cc @tianon ^^ |
|
Yeah sorry, the server filled up thanks to several base updates in a row and then took a long time to churn through the queue; it should be fixed/finished now! |
|
No worries! I don't think there was an urgency in this specific update of Go. Kicking jenkins to see if it goes green; thanks! |
full diff: golang/go@go1.13.10...go1.13.11
go1.13.11 (released 2020/05/14) includes fixes to the compiler. See the Go 1.13.11
milestone on the issue tracker for details:
https://github.com/golang/go/issues?q=milestone%3AGo1.13.11+label%3ACherryPickApproved