Misc #20810
closedRe-enable s390x CI Builds on Master Branch in Travis CI
Description
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.
Updated by nobu (Nobuyoshi Nakada) 12 days ago
- Tracker changed from Bug to Misc
- ruby -v deleted (
master) - Backport deleted (
3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN)
Updated by k0kubun (Takashi Kokubun) 12 days ago ยท Edited
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's successfully running on ruby_3_3.
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?
Updated by k0kubun (Takashi Kokubun) 12 days ago
- Status changed from Open to Feedback
Updated by nagachika (Tomoyuki Chikanaga) 12 days ago
On ruby_3_2, recently all the Travis-CI pipelines are dropped.
https://github.com/ruby/ruby/commit/4873bbd6cc25311fb477bb8fe823d2ea16299717
Updated by jaruga (Jun Aruga) 11 days ago
I sent the following PR to reenable Travis CI including s390x on the rury/ruby master branch.
https://github.com/ruby/ruby/pull/11948
Updated by jaruga (Jun Aruga) 11 days ago
- Status changed from Feedback to Closed
Travis CI including the s390x was reenabled on the ruby/ruby master branch by the above PR.