Skip to content

cmd/go: TestScript/get_insecure_env failure due to 503 from appspot server #54608

Open
@bcmills

Description

@bcmills
#!watchflakes
post <- pkg ~ `^cmd/go` && `(appspot.com|rsc.io).*: 503`

https://build.golang.org/log/730ebecd883624c6969c8bc33d3c34c705ce508a:

go test proxy running at GOPROXY=http://127.0.0.1:37473/mod
--- FAIL: TestScript (0.01s)
    --- FAIL: TestScript/get_insecure_env (2.19s)
        script_test.go:282: 
            # (2022-08-22T19:30:35Z)
            # GOPATH: Set up (0.000s)
            # GOPATH: Try go get -d of HTTP-only repo (should fail). (0.084s)
            # GOPATH: Try again with invalid GOINSECURE (should fail). (0.052s)
            # GOPATH: Try with correct GOINSECURE (should succeed). (2.050s)
            > env GOINSECURE=insecure.go-get-issue-15410.appspot.com/pkg/p
            > go get -d insecure.go-get-issue-15410.appspot.com/pkg/p
            [stderr]
            package insecure.go-get-issue-15410.appspot.com/pkg/p: unrecognized import path "insecure.go-get-issue-15410.appspot.com/pkg/p": reading https://insecure.go-get-issue-15410.appspot.com/pkg?go-get=1: 503 Service Unavailable
            [exit status 1]
            FAIL: testdata/script/get_insecure_env.txt:16: unexpected command failure
            
FAIL
FAIL	cmd/go	731.739s

While I'm shoving stuff into the local test server for #27494, may as well do this test too. 😅

Metadata

Metadata

Assignees

No one assigned

    Labels

    GoCommandcmd/goNeedsFixThe path to resolution is known, but the work has not been done.TestingAn issue that has been verified to require only test changes, not just a test failure.

    Type

    No type

    Projects

    Status

    Active

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions