Arm64: sudo: unable to resolve host *: Name or service not known

Environments Multi CPU Architecture
1

Some issues are happening on Travis arm64 pipeline right now.

Worker information
sudo: unable to resolve host travis-job-junaruga-ruby-612381455: Name or service not known
sudo: unable to resolve host travis-job-junaruga-ruby-612381455: Name or service not known
...
2

We have to set always the allow_failures in the multiple CPU pipelines in the current unstable infra. It’s hard to find when the new failures are added in the situation.

3

I even cannot open the page below properly.

Travis status page shows no problem.

4

It’s nice and helpful to see Travis’s public announcements about the issues on the page below!

https://www.traviscistatus.com/

  • Monitoring - Issue found and fixed. Monitoring system.
    Oct 28, 2023 - 13:00 UTC
  • Investigating - Travis API errors discovered. Builds may be breaking.
    Oct 28, 2023 - 12:15 UTC
5

Now I see that Travis doesn’t trigger the jobs.

https://www.traviscistatus.com/
Resolved - Operation back to normal.
Oct 28, 13:32 UTC

I don’t think this is truth.

6

The builds are starting. But the ppc64le build doesn’t start yet.