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
cmd/go, cmd/go/internal/mod{conv,fetch,load}: tests use GOPROXY from environment #30571
Comments
Change https://golang.org/cl/165745 mentions this issue: |
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. Updates #30571 Change-Id: I447776dff98bd8ee6eb5055b897b9c7d293e3423 Reviewed-on: https://go-review.googlesource.com/c/go/+/165745 Run-TryBot: Bryan C. Mills <bcmills@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
Change https://golang.org/cl/167084 mentions this issue: |
Change https://golang.org/cl/167086 mentions this issue: |
I typo'd this variable in CL 165745, and neither I, the reviewer, nor the TryBots noticed. But the longtest builder noticed, and it's not happy about it. Updates #30571 Change-Id: I5e3d267346407855ec0d1f340a72dc2c521ecc63 Reviewed-on: https://go-review.googlesource.com/c/go/+/167086 Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Change https://golang.org/cl/199820 mentions this issue: |
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 Reviewed-on: https://go-review.googlesource.com/c/go/+/165745 Run-TryBot: Bryan C. Mills <bcmills@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-on: https://go-review.googlesource.com/c/go/+/199820 Run-TryBot: Filippo Valsorda <filippo@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
Change https://golang.org/cl/200037 mentions this issue: |
…et modfetch proxy URL in tests Updates #30571 Fixes #34789 Change-Id: Id4c74e83ee58a080d1c2894ae5ebdbf4aeb1ce42 Reviewed-on: https://go-review.googlesource.com/c/go/+/167084 Run-TryBot: Bryan C. Mills <bcmills@google.com> Reviewed-by: Jay Conrod <jayconrod@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> (cherry picked from commit bd680d9) Reviewed-on: https://go-review.googlesource.com/c/go/+/200037
On tip, the following tests use the GOPROXY environment variable set in environment, and fail if it is set to a Go proxy that isn't functional:
The typical errors is like:
Can be reproduced by doing:
I suspect these tests should be controlling their own GOPROXY environment (i.e., setting it to
direct
). /cc @bcmillsThe text was updated successfully, but these errors were encountered: