Skip to content
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/build, cmd/go: TestGoGetInsecure failing in release-branch.go1.12 #33758

bcmills opened this issue Aug 21, 2019 · 2 comments

x/build, cmd/go: TestGoGetInsecure failing in release-branch.go1.12 #33758

bcmills opened this issue Aug 21, 2019 · 2 comments


Copy link

@bcmills bcmills commented Aug 21, 2019

TestGoGetInsecure in cmd/go is currently failing in the linux-amd64-longtest builder on release-branch.go1.12 (

--- FAIL: TestGoGetInsecure (14.49s)
    --- FAIL: TestGoGetInsecure/modules (4.12s)
        go_test.go:3650: running testgo [get -d]
        go_test.go:3650: standard error:
        go_test.go:3650: go get unexpected status ( 410 Gone
        go_test.go:3650: testgo failed as expected: exit status 1
        go_test.go:3653: running testgo [get -d -insecure]
        go_test.go:3653: standard error:
        go_test.go:3653: go get unexpected status ( 410 Gone
        go_test.go:3653: go [get -d -insecure] 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 and to clear GOPROXY for the test (#30571).

@gopherbot gopherbot added this to the Unreleased milestone Aug 21, 2019
@gopherbot gopherbot added the Builders label Aug 21, 2019
@bcmills bcmills modified the milestones: Unreleased, Go1.12.10 Aug 21, 2019
@bcmills bcmills self-assigned this Aug 21, 2019
@FiloSottile FiloSottile modified the milestones: Go1.12.10, Go1.12.11 Sep 25, 2019
@FiloSottile FiloSottile assigned katiehockman and unassigned bcmills Oct 8, 2019
Copy link

@gopherbot gopherbot commented Oct 8, 2019

Change mentions this issue: [release-branch.go1.12] cmd/go: clear GOPROXY in TestGoGetInsecure

Copy link

@gopherbot gopherbot commented Oct 8, 2019

Closed by merging d7dd91a to release-branch.go1.12.

@gopherbot gopherbot closed this Oct 8, 2019
gopherbot pushed a commit that referenced this issue Oct 8, 2019
TestGoGetInsecure verifies that 'go get -insecure' can fetch a
particular package. However, the GOPROXY protocol does not provide a
means for proxies to indicate packages as insecure; thus, proxies
cannot safely serve those packages.

This also squashes the typo fix from CL 167086.

Updates #30571
Fixes #33758

Change-Id: I447776dff98bd8ee6eb5055b897b9c7d293e3423
Run-TryBot: Bryan C. Mills <>
Reviewed-by: Brad Fitzpatrick <>
TryBot-Result: Gobot Gobot <>
Run-TryBot: Filippo Valsorda <>
Reviewed-by: Bryan C. Mills <>
@katiehockman katiehockman modified the milestones: Go1.12.11, Go1.12.12 Oct 17, 2019
@golang golang locked and limited conversation to collaborators Oct 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants