Issue #20013 has been updated by jaruga (Jun Aruga). It seems that s390x build takes time to start. But the builds are still running. https://app.travis-ci.com/github/ruby/ruby/builds ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-105381 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). I will enable allow_failures for s390x. I am sorry for that. https://github.com/ruby/ruby/pull/8997 ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-105383 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). I will drop the s390x temporarily. I guess that there are maximum queue number in Travis CI. And as s390x builds are in the queue, other CPU architecture builds (arm64, arm32, ppc64le) even don't start. https://github.com/ruby/ruby/pull/9004 ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-105387 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). I can see Travis CI builds are stable except for s390x. https://app.travis-ci.com/github/ruby/ruby/builds I am communicating with Travis CI support. It seems they added "IBM Z Builds" in Build Processing on Travis CI status page. And you see the status is Degraded Performance (yellow color). It's really helpful! I am asking them to add the "Arm builds" / "IBM ppc64le builds" on the page too. https://www.traviscistatus.com/ ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-105392 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). I tested the PR to add the s390x on my forked repository, and merged it. Now Travis CI has the s390x pipeline again. ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-105400 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). Now I am asking Travis CI support by emailing them about the following error messages which are printed in only Arm64 pipelines, and it seems not affected to the result of the CI tests. https://app.travis-ci.com/github/ruby/ruby/jobs/615194806#L6 ``` sudo: unable to resolve host travis-job-ruby-ruby-615194806: Name or service not known ``` I opened the thread about the issue in the end of the October 2023, but I haven't seen the response there. https://travis-ci.community/t/arm64-sudo-unable-to-resolve-host-name-or-ser… So, I emailed them today, and then I was told that the support has reached out to the Travis infra team. I will let you know here when I have updates. ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-105829 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). 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 ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-106528 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). I tested. I sent a PR to add the s390x again. https://github.com/ruby/ruby/pull/9773 ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-106538 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). It seems some s390x builds are not starting after 3 hours now. I am asking Travis customer support. https://app.travis-ci.com/github/ruby/ruby/builds https://app.travis-ci.com/github/ruby/ruby/builds/269093276 https://app.travis-ci.com/github/ruby/ruby/builds/269093679 https://www.traviscistatus.com/ - Builds Processing - IBM Z Builds shows operational (green). ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-106954 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). jaruga (Jun Aruga) wrote in #note-19: Today I found another s390x build exceeding the maximum timeout 50 minutes. Interestingly it took the `make test-all` build time for 588 seconds (= about 9 minutes). That is normal. https://app.travis-ci.com/github/ruby/ruby/jobs/618265449#L2095 But it seems that a freezing happened in the step of the `make test-spec`. https://app.travis-ci.com/github/ruby/ruby/jobs/618265449#L3079 ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-106961 * 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/

Issue #20013 has been updated by Eregon (Benoit Daloze). FYI mspec has a `--timeout SECONDS` option, which should help identify which spec is hanging/very slow. ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-106965 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). We have observed unstable Travis ppc64le/s390x pipelines. So, I added the allow_failures to the pipelines by the PR <https://github.com/ruby/ruby/pull/10158>. ## ppc64le We have seen the following errors around 10 or more times in latest 1 or 2 days. * https://app.travis-ci.com/github/ruby/ruby/builds/269211469 * https://app.travis-ci.com/github/ruby/ruby/builds/269204073 * https://app.travis-ci.com/github/ruby/ruby/builds/269211464 ## s390x The following error happened without any output. * https://app.travis-ci.com/github/ruby/ruby/builds/269201221 ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-107099 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). jaruga (Jun Aruga) wrote in #note-21: 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/

Issue #20013 has been updated by jaruga (Jun Aruga). jaruga (Jun Aruga) wrote in #note-28: I sent the PR for that. https://github.com/ruby/ruby/pull/10180 ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-107132 * 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/

Issue #20013 has been updated by jaruga (Jun Aruga). For you information, I saw the following ppc64le job not starting 10 days ago, and contacted Travis support at that time, and still waiting for the fix, though I didn't find any other failures in last few days. https://app.travis-ci.com/github/ruby/ruby/jobs/619005133 Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-beca… The build has been terminated ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-107410 * 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/