cmd/go: modules eagerly downloaded even with populated cache #36258
Comments
What happens if you let At first blush, this looks like an instance of #26152. |
It's pretty hard to reproduce this without flaky internet (just turning the wifi off doesn't surface the issue.) I'll keep an eye out for if it shows up in the meantime, I guess? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Turned off my network and ran
go test ./...
What did you expect to see?
My tests run.
What did you see instead?
Blocking and searching for modules:
This is weird. It doesn't reproduce every time, but I notice it a lot more now while I'm outside of Los Angeles, visiting family in TX where the internet is worse. To be clear: I already have a populated go module cache, so I should only need to download modules when I update my
go.mod
, which is pretty rare. I don't think this is new with 1.14, I just think it's related to the worse internet over the holidays.The text was updated successfully, but these errors were encountered: