-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: TestScript use of localhost GOPROXY failing on Windows, now skipped #26457
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
Comments
Change https://golang.org/cl/124857 mentions this issue: |
I don't know why it's failing. Filed #26457. Change-Id: I84833293a572c5a1a25135bd01cb88518fc7441e Reviewed-on: https://go-review.googlesource.com/124857 Run-TryBot: Russ Cox <[email protected]> Reviewed-by: Russ Cox <[email protected]>
It looks like this might happen when some environment variables are missing: gevent/gevent#284 I don’t have Windows so I can’t check further. |
I agree. Russ's error looks similar to #25210. I did not investigate this bug (I do not have Windows PC near by), but Brad's problem was that he created Windows process with no environment variables. Generally you cannot do that. You should copy your current process variables and add / delete / modify whatever variables you want. Alex |
That makes sense, thanks - that comment saves me a ton of time. I am trying to make sure extraneous env vars don't pollute the tests but I'll copy whatever Windows needs. |
Change https://golang.org/cl/124858 mentions this issue: |
cmd/go's tests start an HTTP server by doing net.Listen("tcp", "localhost:0") and then try to make URLs using l.Addr().String(), which ends up being
localhost:<port>
.This worked for some tests but somehow is failing when run as part of TestScript, as of CL 124697.
I can't see what is different between the old hand-written-in-Go tests and the new script-based tests.
One possibility was the use of t.Parallel, but I commented that out in TestScript and still no luck.
The trybots failed on that CL and the gomote failed too when run by hand. I submitted it anyway to see if the builders were any different, since it is so mysterious. I expect them to fail too. If they do I will skip those scripts on Windows.
We need to turn the script tests back on for Windows before the release.
I also tried using [::1]:0 instead of localhost:0 and it did not help.
The text was updated successfully, but these errors were encountered: