4 Mar
2024
4 Mar
'24
12:23 p.m.
Issue #20013 has been updated by jaruga (Jun Aruga).
jaruga (Jun Aruga) wrote in #note-21:
jaruga (Jun Aruga) wrote in #note-19:
> We are seeing one of s390x build[1] is very slow, exceeding the maximum timeout 50
minutes, totally taking the `make test-all` build time for 1515 seconds (= about 25
minutes) So far this build is only the case. This behavior is not normal. Because the next
build[2] takes total 28 minutes 40 seconds, taking the `make test-all` build time 683
seconds (= about 11 minutes). I suspect this may come from a specific slow running
machine. And I am asking Travis support about this issue.
For the slow s390x build issue, I received the following reply from Travis support on 1st
March 2024.
*Our Infra team has resolved the issue you encountered. In case it resurfaces, please
reach back and we will gladly help.*
----------------------------------------
Misc #20013: Travis CI status
https://bugs.ruby-lang.org/issues/20013#change-107118
* 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/