Open
Description
#!watchflakes
post <- (pkg ~ `^cmd/go` || pkg ~ `^golang.org/x/mod`) && (
`Failed to connect to github.com port 443: Connection refused` ||
`remote: Internal Server Error.` ||
`error: RPC failed; HTTP 500` ||
`GnuTLS recv error` ||
`The TLS connection was non-properly terminated` ||
`connect: network is unreachable` ||
`502 Bad Gateway` ||
`remote: Repository not found.` ||
`The requested URL returned error: 50\d` ||
`system library:.*:Connection reset by peer` ||
`dial tcp .*: i/o timeout` ||
`Failed to connect to .* port .*: Connection timed out` ||
`Failed to connect to .* port .*: Operation timed out` ||
`Empty reply from server` ||
`Could not resolve host:` ||
`Failed to connect to .* port 443 .*: Couldn't connect to server` ||
`read: connection reset by peer`)
cmd/go's tests flake when the network is having trouble (or the servers on the other end are).
This should only happen on the longtest builders.
This issue gathers reports so we can watch the frequency.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Active