-
Notifications
You must be signed in to change notification settings - Fork 264
Add go 1.11.0 #499
Add go 1.11.0 #499
Conversation
|
Alright, looks like there are some failures; edit: Details
output on 1.11Difference between 1.10 and 1.11: 1.10 1.11 |
|
Ok, so definitely something weird with test.go: package test
type MyStruct struct {}
func test(mystructs []*MyStruct) *MyStruct {
var foo *MyStruct
for _, mystruct := range mystructs {
foo := mystruct
}
return foo
}Go 1.10.3: /usr/local/go/bin/go vet --shadow .
# _/foo
./test.go:7:3: foo declared and not usedGo 1.11beta1: /usr/local/go/bin/go vet --shadow .
# _/foo
./test.go:7:3: foo declared and not used
# _/foo
./test.go:7:3: foo declared but not used
vet: typecheck failures |
|
Opened an issue upstream golang/go#26222 |
|
my issue was marked as a duplicate of golang/go#26125 (which is labeled "release blocker", so should be fixed before Go 1.11 final) |
|
Updated to Go 1.11beta2; |
This seems to be the problem with a particular linter, It looks like |
|
@kolyshkin thanks! I arrived at the same conclusion yesterday, and found that PR for the rename; haven't tried yet, but I could temporarily cherry-pick that PR here to check if the latest version resolved the problem |
|
cherry-picked #505 into this PR to see if that resolves the issue |
|
Looks good! All green with that patch applied |
|
I tested manually before, it was working. Heck, I almost created a dupe of #505... |
fe3ea80 to
1f32491
Compare
|
Updated to 1.11beta3 |
|
go 1.11rc1 is out (no docker images as of yet) |
|
images have been updated to rc1 $ cat Dockerfile
FROM golang:1.11-rc
RUN go version$ docker build .
Sending build context to Docker daemon 2.048kB
Step 1/2 : FROM golang:1.11-rc
1.11-rc: Pulling from library/golang
55cbf04beb70: Pull complete
1607093a898c: Pull complete
9a8ea045c926: Pull complete
d4eee24d4dac: Pull complete
9c35c9787a2f: Pull complete
a586ab591509: Pull complete
fb94d9d3eaaf: Pull complete
Digest: sha256:848d7c6e26a6ca99bdf50ae952769998f4ffd458328e2f4089ba8e784b09ffd7
Status: Downloaded newer image for golang:1.11-rc
---> 798d75db8922
Step 2/2 : RUN go version
---> Running in 1a480348c540
go version go1.11rc1 linux/amd64
Removing intermediate container 1a480348c540
---> cfa17a33c4fd
Successfully built cfa17a33c4fd |
1f32491 to
5a01736
Compare
|
Thanks for the ping! Updated the PR to 1.11rc1 |
|
The official 1.11.0 image has also been released if you want to update it to that. |
Signed-off-by: Sebastiaan van Stijn <[email protected]>
Signed-off-by: Sebastiaan van Stijn <[email protected]>
5a01736 to
5c5c8cd
Compare
| go: | ||
| - 1.9.x | ||
| - 1.10.x | ||
| - 1.11 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be changed to 1.11.x once the first patch release for Go 1.11 is out (erm, unless I remember incorrectly, but I seem to recall .x didn't work if there's no patch release yet)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.11.x seems to work well for several of my repos, FYI.
There were some problems with Go 1.10, since YAML and some other code parsed 1.10 a a number (1.1), so perhaps that is what you are recalling?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember that 1.10 is a JSON number, which is identical to 1.1 -- for an actual 1.10 you want "1.10" to force it to a string!
|
@robinjoseph08 thanks for the ping! I was waiting for those images to arrive indeed, but forgot to update Yesterday 😅 PR is updated, and should be ready for review now |
|
Thanks! |
|
Ah, yes that may have been it!
… On 1 Sep 2018, at 13:43, Martin Tournoij ***@***.***> wrote:
@Carpetsmoker commented on this pull request.
In .travis.yml:
> @@ -6,6 +6,7 @@ install:
go:
- 1.9.x
- 1.10.x
+- 1.11
1.11.x seems to work well for several of my repos, FYI.
There were some problems with Go 1.10, since YAML and some other code parsed 1.10 a a number (1.1), so perhaps that is what you are recalling?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Adding Go 1.11 to travis to catch possible issues; I can update this PR when newer betas are released
/cc @dnephin @kolyshkin