Repeated network errors (timeouts) duing builds

We seem to have repeated network errors on a number of our builds recently.

Example is here: https://travis-ci.org/apache/airflow/jobs/646256516?utm_medium=notification&utm_source=email

It is just one example where we failed to reach two different apache backup servers (it’s highly unlikely to happen at the same time). We had also other - similarly looking errors with different network server - this indicates some problem with the underlying network infrastructure.

Downloading KEYS from backup Apache servers: https://www-eu.apache.org/dist/creadur/KEYS, https://www-us.apache.org/dist/creadur/KEYS
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:31 --:--:--     0curl: (7) Failed to connect to www-eu.apache.org port 443: Connection timed out
+ curl --fail --location https://www-us.apache.org/dist/creadur/KEYS --output /opt/KEYS
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:31 --:--:--     0curl: (7) Failed to connect to www-us.apache.org port 443: Connection timed out

Another example here - with github, so it must be a network issue:

https://travis-ci.org/apache/airflow/jobs/646715557?utm_medium=notification&utm_source=github_status

+ curl --fail --location https://github.com/bolkedebruin/minicluster/releases/download/1.1/minicluster-1.1-SNAPSHOT-bin.zip --output /tmp/minicluster.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   622    0   622    0     0   2058      0 --:--:-- --:--:-- --:--:--  2052
  0     0    0     0    0     0      0      0 --:--:--  0:00:31 --:--:--     0curl: (7) Failed to connect to github-production-release-asset-2e65be.s3.amazonaws.com port 443: Connection timed out

The errors ar still there even for Travis’ own parts:

https://travis-ci.org/apache/airflow/jobs/647277664?utm_medium=notification&utm_source=email

curl: (6) Could not resolve host: cli-assets.heroku.com
xz: (stdin): File format not recognized
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Failed to update Heroku CLI

Is there anything Travis support can do with it?

Hi,

I think we’re having a similar issue. For us Docker pulls time out: Docker pull fails often.

1 Like
Imprint