[ruby-core:119599] [Ruby master Bug#20810] Re-enable s390x CI Builds on Master Branch in Travis CI
Issue #20810 has been reported by mayur.jadhav (Mayur Jadhav). ---------------------------------------- Bug #20810: Re-enable s390x CI Builds on Master Branch in Travis CI https://bugs.ruby-lang.org/issues/20810 * Author: mayur.jadhav (Mayur Jadhav) * Status: Open * ruby -v: master * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Description: Currently, the Travis CI has been temporarily disabled on the master branch via Pr(https://github.com/ruby/ruby/pull/11509). However, the s390x builds are successfully running on other branches( ruby_3_3, ruby_3_2) on Travis CI, which were previously experiencing timeouts. The issue has been addressed by the Travis team. Given the significance of multi-architecture support for Ruby, we request that the Travis CI builds be re-enabled on the master branch. please let us know we are more than happy to collaborate to make this happen. Thanks. -- https://bugs.ruby-lang.org/
Issue #20810 has been updated by k0kubun (Takashi Kokubun).
However, the s390x builds are successfully running on other branches( ruby_3_3, ruby_3_2) on Travis CI, which were previously experiencing timeouts.
The latest result of ruby_3_3 is a timeout https://app.travis-ci.com/github/ruby/ruby/jobs/627323862. I'm not sure if it works for other branches either.
please let us know we are more than happy to collaborate to make this happen
Could you investigate why the above job failed and file a PR to fix it? ---------------------------------------- Misc #20810: Re-enable s390x CI Builds on Master Branch in Travis CI https://bugs.ruby-lang.org/issues/20810#change-110222 * Author: mayur.jadhav (Mayur Jadhav) * Status: Open ---------------------------------------- Description: Currently, the Travis CI has been temporarily disabled on the master branch via Pr(https://github.com/ruby/ruby/pull/11509). However, the s390x builds are successfully running on other branches( ruby_3_3, ruby_3_2) on Travis CI, which were previously experiencing timeouts. The issue has been addressed by the Travis team. Given the significance of multi-architecture support for Ruby, we request that the Travis CI builds be re-enabled on the master branch. please let us know we are more than happy to collaborate to make this happen. Thanks. -- https://bugs.ruby-lang.org/
Issue #20810 has been updated by nagachika (Tomoyuki Chikanaga). On ruby_3_2, recently all the Travis-CI pipelines are dropped. https://github.com/ruby/ruby/commit/4873bbd6cc25311fb477bb8fe823d2ea16299717 ---------------------------------------- Misc #20810: Re-enable s390x CI Builds on Master Branch in Travis CI https://bugs.ruby-lang.org/issues/20810#change-110224 * Author: mayur.jadhav (Mayur Jadhav) * Status: Feedback ---------------------------------------- Description: Currently, the Travis CI has been temporarily disabled on the master branch via Pr(https://github.com/ruby/ruby/pull/11509). However, the s390x builds are successfully running on other branches( ruby_3_3, ruby_3_2) on Travis CI, which were previously experiencing timeouts. The issue has been addressed by the Travis team. Given the significance of multi-architecture support for Ruby, we request that the Travis CI builds be re-enabled on the master branch. please let us know we are more than happy to collaborate to make this happen. Thanks. -- https://bugs.ruby-lang.org/
Issue #20810 has been updated by jaruga (Jun Aruga). I sent the following PR to reenable Travis CI including s390x on the rury/ruby master branch. https://github.com/ruby/ruby/pull/11948 ---------------------------------------- Misc #20810: Re-enable s390x CI Builds on Master Branch in Travis CI https://bugs.ruby-lang.org/issues/20810#change-110232 * Author: mayur.jadhav (Mayur Jadhav) * Status: Feedback ---------------------------------------- Description: Currently, the Travis CI has been temporarily disabled on the master branch via Pr(https://github.com/ruby/ruby/pull/11509). However, the s390x builds are successfully running on other branches( ruby_3_3, ruby_3_2) on Travis CI, which were previously experiencing timeouts. The issue has been addressed by the Travis team. Given the significance of multi-architecture support for Ruby, we request that the Travis CI builds be re-enabled on the master branch. please let us know we are more than happy to collaborate to make this happen. Thanks. -- https://bugs.ruby-lang.org/
Issue #20810 has been updated by jaruga (Jun Aruga). Status changed from Feedback to Closed Travis CI including the s390x was reenabled on the ruby/ruby master branch by the above PR. ---------------------------------------- Misc #20810: Re-enable s390x CI Builds on Master Branch in Travis CI https://bugs.ruby-lang.org/issues/20810#change-110234 * Author: mayur.jadhav (Mayur Jadhav) * Status: Closed ---------------------------------------- Description: Currently, the Travis CI has been temporarily disabled on the master branch via Pr(https://github.com/ruby/ruby/pull/11509). However, the s390x builds are successfully running on other branches( ruby_3_3, ruby_3_2) on Travis CI, which were previously experiencing timeouts. The issue has been addressed by the Travis team. Given the significance of multi-architecture support for Ruby, we request that the Travis CI builds be re-enabled on the master branch. please let us know we are more than happy to collaborate to make this happen. Thanks. -- https://bugs.ruby-lang.org/
participants (4)
-
jaruga (Jun Aruga) -
k0kubun (Takashi Kokubun)
-
mayur.jadhav (Mayur Jadhav)
-
nagachika (Tomoyuki Chikanaga)