Issue #20013 has been updated by jaruga (Jun Aruga).
jaruga (Jun Aruga) wrote in #note-14:
I will drop the s390x case in Travis CI temporarily. I
am not sure that the issue comes from an infra or Ruby. But right now the test failing
with 50 minutes is not convenient as a CI.
https://github.com/ruby/ruby/pull/9758
I got a message from Travis CI support "Our Infra team has deployed a fix for the
issue you encountered with the s390x Build environment."
Now I am testing the Travis s390x on my forked repository.
----------------------------------------
Misc #20013: Travis CI status
https://bugs.ruby-lang.org/issues/20013#change-106533
* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
----------------------------------------
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/