Tracking issue for spurious network failures on bots

[alexcrichton]

I'm hoping to catalog network failures on the bots here just to keep an eye on the rate that they're happening as well as common failure modes. If they're common enough we should investigate solutions.

github errors

• https://travis-ci.org/rust-lang/rust/jobs/217835684 - failed to clone repo
• https://travis-ci.org/rust-lang/rust/jobs/217834828 - failed to clone repo

Submodule clone timeout

https://travis-ci.org/rust-lang/rust/jobs/210363616

Cloning into '/home/travis/build/rust-lang/rust/src/llvm'...

No output has been received in the last 30m0s, this potentially indicates a stalled build or something wrong with the build itself.

Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

The build has been terminated

Fixed faiulres

Failure to fetch OpenSSL tarball

Fixed by #40545

https://travis-ci.org/rust-lang/rust/jobs/211285568

curl: (7) Failed to connect to www.openssl.org port 443: Connection refused


command did not execute successfully: "curl" "-o" "/checkout/obj/build/mipsel-unknown-linux-gnu/openssl/openssl-1.0.2k.tar.tmp" "https://www.openssl.org/source/openssl-1.0.2k.tar.gz"
expected success, got: exit code: 7

CentOS 5 urls changed

https://travis-ci.org/rust-lang/rust/jobs/218179477

hopefully fixed by #41045

CentOS 5.11 become EOL, apparently the base image failed to keep succeeding at yum update

Crates.io errors

Presumed bug in Cargo

• https://travis-ci.org/rust-lang/rust/jobs/214573195 - during cargotest
• https://travis-ci.org/rust-lang/rust/jobs/214511796 - during cargotest
• https://ci.appveyor.com/project/rust-lang/rust/build/1.0.2517/job/78c29lc858e7a0nh - corrupt download?

[ishitatsuyuki]

Travis uses GCE and I suppose Google won't have problems with their high quality networking, so I guess this is some kind of anti-DDoS triggered. One way is to mirror, and another way is to force them into build cache.

Psst... using Google Cloud Storage will make the transfers completely inside Google's Cloud and potentially decreases: latency, errors, and egress bill.