Issue #20013 has been updated by jaruga (Jun Aruga). Right now I am seeing Travis's arm64 (and arm32) take time around 7 hours to start the jobs. Therefore I will allow failures for the cases to avoid waiting for the jobs. https://app.travis-ci.com/github/ruby/ruby/builds/272105049 https://app.travis-ci.com/github/ruby/ruby/builds/272105708 This is the PR. Sorry for your inconvenience. https://github.com/ruby/ruby/pull/11509 ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-109567 * Author: jaruga (Jun Aruga) * Status: Open ---------------------------------------- I would like to use this ticket to manage our activities to report Travis CI status. Because there is Travis CI status page provided by Travis CI. However, even when the page shows ok, I actually see infra issues. https://www.traviscistatus.com/ I would share my activities and report the Travis CI status on the ticket. The ticket's status is not closed until we stop using Travis CI. The easiest option to fix the Travis infra issue is to email Travis CI support `support _AT_ travis-ci.com`. You can check [this ruby/ruby Travis CI wiki page](https://github.com/ruby/ruby/wiki/CI-Servers#travis-ci) for details. -- https://bugs.ruby-lang.org/