Open dmitshur opened 2 years ago
That's weird, the logs shows that enviroment is GOPROXY=https://goproxy.io,direct
cc @oiooj
greplogs -l -e '(?ms)\Alinux-amd64-wsl.*unexpected EOF' --since=2022-08-04
2022-09-09T18:28:35-c4649c6-e509452/linux-amd64-wsl
2022-09-09T17:18:21-c1b48ff-31d06b5/linux-amd64-wsl
2022-09-09T15:35:30-eeaf4eb-8618858/linux-amd64-wsl
2022-09-08T14:33:45-b0ca10f-e5ed221/linux-amd64-wsl
2022-09-07T16:00:20-7033275/linux-amd64-wsl
2022-09-03T18:39:45-c86fa9a-a73506c/linux-amd64-wsl
2022-08-31T15:33:00-4dea5cf-fa0e3bf/linux-amd64-wsl
Thanks! All errors occured on goproxy.io
while another builder is using goproxy.cn
.
I think that confirms my guess that this is a server side issue.
The errors should be fixed if nothing else. I've seen things like:
godoc/redirect/redirect.go:22:2: golang.org/x/net@v0.0.0-20211015210444-4f30a5c0130f: unexpected EOF
which is not terribly clear. It should be more like a usual network failure.
Found new matching dashboard test flakes for:
#!watchflakes
post <- builder == "linux-amd64-wsl" && `\.go:\d+:\d+: .*@v\d.*: unexpected EOF`
The errors should be fixed if nothing else.
That's #52727, fixed at head (but not backported, and many of these occur on x/ repos on release branches).
It should be more like a usual network failure.
Unfortunately that is the usual network failure produced by net/http
if the connection reads less than the declared Content-Length
from the response body.
I don't think the fundamental problem can be fixed in a way that preserves backward compatibility, but I did add a comment in https://github.com/golang/go/issues/5465#issuecomment-1127980361. (Compare #53472.)
Found new dashboard test flakes for:
#!watchflakes
post <- builder == "linux-amd64-wsl" && `\.go:\d+:\d+: .*@v\d.*: unexpected EOF`
Found new dashboard test flakes for:
#!watchflakes
post <- builder == "linux-amd64-wsl" && `\.go:\d+:\d+: .*@v\d.*: unexpected EOF`
Found new dashboard test flakes for:
#!watchflakes
post <- builder == "linux-amd64-wsl" && `\.go:\d+:\d+: .*@v\d.*: unexpected EOF`
From https://build.golang.org/log/1d606b9af9022065aa9b7b4dd76799415ae5fd0b:
The "https:/goproxy.io" part looks unusual, should that be "https://" instead of "https:/"? CC @mengzhuo.
Possibly related to #52793, #52727, #42971, but they're all closed.