-
Notifications
You must be signed in to change notification settings - Fork 89
Conversation
fmt.Println seems to have changed location between go1.9 and tip.
@Contextualist do you mind taking a look? The only thing failing now on go1.10 is completiion:
|
langserver/langserver_test.go
Outdated
@@ -449,7 +449,7 @@ package main; import "test/pkg"; func B() { p.A(); B() }`, | |||
// "a.go:1:53": "type int int", | |||
}, | |||
overrideGodefDefinition: map[string]string{ | |||
"a.go:1:40": "/goroot/src/fmt/print.go:256:6-256:13", // hitting the real GOROOT | |||
"a.go:1:71": "/goroot/src/fmt/print.go:38:6-38:11", // hitting the real GOROOT |
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.
Every small change in the src will fail this test case. Is there a better approach to this? Maybe just assert that a valid file and line number is returned?
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.
yeah that sounds much better. It requires a bit of cleaning up in our tests, but that seems fine given this is relying on GOROOT of the user running the tests. Right now the location I have picked hasn't changed in 2 years.
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.
Updated to test path instead for this specific test.
This reverts commit aeb751f.
go1.10 introduces the cache directory. So now objects will only appear in `pkg` if they are explicitly installed. Previous versions of go would create entries for the transitive dependencies. So for our vendor tests running `go install -i ...` would not create a corresponding file in `pkg` for the vendored packages since `...` does not list vendor. Using `all` instead does include the vendored pkg, so will include the vendored pkgs. This will likely have wider effects on go tooling that rely on pkg. Already filed nsf/gocode#500 for gocode.
@keegancsmith Ah! Thanks for fixing the vendor issue. I just found that .a files for vendor packages are missing, never had thought that it is the problem due to go 1.10 package caching. |
@Contextualist yeah sorry I should of mentioned I decided to look into it. |
bb86aea
to
1486a12
Compare
@keegancsmith That's totally fine. 😄 Appreciate your efficiency! Nonetheless, we have to wait for |
We need to sort out our tests, they currently fail.