-
Notifications
You must be signed in to change notification settings - Fork 714
Closed
Description
We from rust-lang/rust have experienced a high rate of "Couldn't resolve host" errors since 2018-05-24, and it still persist till today. All errors happen inside Docker in sudo: required jobs. An interesting observation is that the error always happen around 06:30Z to 07:15Z, so I suspect there's some cron configuration problem.
The following lists the logs we've gathered that were affected by this bug. The timestamp is when we see the job has failed.
| Timestamp | Log | Error |
|---|---|---|
| 2018-05-24T07:14:12Z | https://api.travis-ci.org/v3/job/383034809/log.txt | fatal: unable to access 'https://github.com/rust-lang-nursery/rust-toolstate.git/': Could not resolve host: github.com |
| 2018-05-26T06:34:00Z | https://api.travis-ci.org/v3/job/383995388/log.txt | curl: (6) Could not resolve host: s3-us-west-1.amazonaws.com |
| 2018-05-27T07:02:13Z | https://api.travis-ci.org/v3/job/384282776/log.txt | fatal: unable to access 'https://github.com/rust-lang-nursery/rust-toolstate.git/': Could not resolve host: github.com |
| 2018-05-29T06:50:07Z | https://api.travis-ci.org/v3/job/385031055/log.txt | curl: (6) Could not resolve host: s3-us-west-1.amazonaws.com |
| 2018-05-30T06:47:00Z | https://api.travis-ci.org/v3/job/385518123/log.txt | fatal: unable to access 'https://github.com/BurntSushi/xsv/': Could not resolve host: github.com |
| 2018-05-31T06:38:08Z | https://api.travis-ci.org/v3/job/386026639/log.txt | curl: (6) Couldn't resolve host 's3-us-west-1.amazonaws.com' |
| 2018-06-01T06:42:09Z | https://api.travis-ci.org/v3/job/386506502/log.txt | curl: (6) Could not resolve host: s3-us-west-1.amazonaws.com |
| 2018-06-02T06:32:08Z | https://api.travis-ci.org/v3/job/386992985/log.txt | curl: (6) Could not resolve host: s3-us-west-1.amazonaws.com |
| 2018-06-03T07:10:07Z | https://api.travis-ci.org/v3/job/387315900/log.txt | curl: (6) Could not resolve host: s3-us-west-1.amazonaws.com |
| 2018-06-05T07:14:48Z | https://api.travis-ci.org/v3/job/388108259/log.txt | curl error: Couldn't resolve host 'github.com' |
| 2018-06-07T06:44:09Z | https://api.travis-ci.org/v3/job/389090019/log.txt | curl: (6) Could not resolve host: s3-us-west-1.amazonaws.com |
- Our current
.travis.yml: https://github.com/rust-lang/rust/blob/edae1cc38b467518a8eea590c9c3e0c103b4ecb0/.travis.yml - The script which starts docker: https://github.com/rust-lang/rust/blob/edae1cc38b467518a8eea590c9c3e0c103b4ecb0/src/ci/docker/run.sh
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels