ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "k0kubun (Takashi Kokubun) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "k0kubun (Takashi Kokubun)" <noreply@ruby-lang.org>
Subject: [ruby-core:119600] [Ruby master Misc#20810] Re-enable s390x CI Builds on Master Branch in Travis CI
Date: Wed, 23 Oct 2024 16:16:02 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-110222.20241023161602.54543@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20810.20241023130836.54543@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/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/

  reply	other threads:[~2024-10-23 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 13:08 [ruby-core:119599] [Ruby master Bug#20810] " mayur.jadhav (Mayur Jadhav) via ruby-core
2024-10-23 16:16 ` k0kubun (Takashi Kokubun) via ruby-core [this message]
2024-10-24  3:03 ` [ruby-core:119601] [Ruby master Misc#20810] " nagachika (Tomoyuki Chikanaga) via ruby-core
2024-10-24 16:17 ` [ruby-core:119610] " jaruga (Jun Aruga) via ruby-core
2024-10-25  5:25 ` [ruby-core:119612] " jaruga (Jun Aruga) via ruby-core

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-110222.20241023161602.54543@ruby-lang.org \
    --to=ruby-core@ml.ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).