Issue #20013 has been updated by jaruga (Jun Aruga). We drop Travis CI for ruby/zlib, ruby/prism too. Because the Travis infra issues are still ongoing since my last report. * https://github.com/ruby/zlib/pull/84 * https://github.com/ruby/prism/pull/3047 The Travis CI status page is not accurate. https://www.traviscistatus.com/ - Past Incidents I still see the jobs are not starting with empty outputs. https://app.travis-ci.com/github/ruby/prism/builds/272244955 ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-109703 * 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/