-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/tools/internal/imports: TestModeGetmodeVendor failing due to vendoring change #34826
Comments
Argh, sorry for the lack of advance warning. I ran the |
Change https://golang.org/cl/200299 mentions this issue: |
Considering the test name, it's probably 199821. I'm guessing that most of
More generally, though, |
Test is broken by recent cmd/go vendoring changes. Skipping the test case while we figure out what to do. Updates golang/go#34826 Change-Id: I31a6f18e40420970251e25836edcf32c56c10ef5 Reviewed-on: https://go-review.googlesource.com/c/tools/+/200299 Run-TryBot: Jay Conrod <[email protected]> Reviewed-by: Bryan C. Mills <[email protected]>
No, it very specifically needs modules, I'm afraid. Listing packages is too slow. I'll talk it through with Jay. |
(It previously reported incomplete module information in If you're detecting |
This comment has been minimized.
This comment has been minimized.
Change https://golang.org/cl/203257 mentions this issue: |
At tip, $GOROOT/src/go.mod is 1.14, $GOROOT/src/vendor exists, and so vendor mode is automatically enabled. That causes golang/go#34826. This will be fixed by my upcoming vendoring CL, but for now skip. Updates golang/go#34826 Change-Id: I5fff51fff54cf83e6369ae76bf3b19cfb7b5ac15 Reviewed-on: https://go-review.googlesource.com/c/tools/+/203257 Run-TryBot: Heschi Kreinick <[email protected]> Run-TryBot: Rebecca Stambler <[email protected]> Reviewed-by: Rebecca Stambler <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
Change https://golang.org/cl/203017 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
no, only tip
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
test passes
What did you see instead?
https://build.golang.org/log/4ca136788f50edc4878fe80c76f1ec376539a9b2
The text was updated successfully, but these errors were encountered: