x/build, cmd/go: TestGoGetInsecure failing in release-branch.go1.12 #33758
Description
TestGoGetInsecure in cmd/go is currently failing in the linux-amd64-longtest builder on release-branch.go1.12 (https://build.golang.org/log/01102088d2b8610a921c538f1beb335acb222c51):
--- FAIL: TestGoGetInsecure (14.49s)
--- FAIL: TestGoGetInsecure/modules (4.12s)
go_test.go:3650: running testgo [get -d insecure.go-get-issue-15410.appspot.com/pkg/p]
go_test.go:3650: standard error:
go_test.go:3650: go get insecure.go-get-issue-15410.appspot.com/pkg/p: unexpected status (http://10.240.0.55:30157/insecure.go-get-issue-15410.appspot.com/pkg/p/@v/list): 410 Gone
go_test.go:3650: testgo failed as expected: exit status 1
go_test.go:3653: running testgo [get -d -insecure insecure.go-get-issue-15410.appspot.com/pkg/p]
go_test.go:3653: standard error:
go_test.go:3653: go get insecure.go-get-issue-15410.appspot.com/pkg/p: unexpected status (http://10.240.0.55:30157/insecure.go-get-issue-15410.appspot.com/pkg/p/@v/list): 410 Gone
go_test.go:3653: go [get -d -insecure insecure.go-get-issue-15410.appspot.com/pkg/p] failed unexpectedly in /workdir/tmp/gotest754988467: exit status 1
panic.go:406: ended in /workdir/tmp/gotest754988467
The failure seems to have something to do with a local proxy running on the builder, possibly from #31770 or #14594.
Probably we just need to backport https://golang.org/cl/165745 and https://golang.org/cl/167086 to clear GOPROXY for the test (#30571).