24 Feb
2024
24 Feb
'24
9:08 a.m.
Issue #20013 has been updated by jaruga (Jun Aruga).
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.
[1] https://app.travis-ci.com/github/ruby/ruby/jobs/618214295#L2094
[2] https://app.travis-ci.com/github/ruby/ruby/jobs/618215618#L2262
I was told from the Travis support that the Travis's engineers were able to check this
issue by their message below.
Thanks so much for your patience here.
Our engineers were able to check on this and you should be able to see your builds are
now running. Very sorry for the trouble and we will continue to monitor this!
----------------------------------------
Misc #20013: Travis CI status
https://bugs.ruby-lang.org/issues/20013#change-106962
* 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/