-
Notifications
You must be signed in to change notification settings - Fork 5.5k
CI: ubuntu-ibm.yml: Add GitHub Actions ppc64le case #14222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
0babe52
to
8fe3709
Compare
The GitHub Actions ppc64le sometimes delays to start the job. In my latest case, I need to wait for the job to start more than 25 minutes. This is a blocker to merge this PR in my opinion. I reported the issue IBM/actionspz#34. |
Some tests in the |
5181a1f
to
c5795eb
Compare
I am seeing many timeout related failures, while the the tests passe on RubyCI Ubuntu (ppc64le) server. I suspect the reason of the failures is a CI machine's slow performance. So, I added the logic to measure the performance of the |
97bf09a
to
603e5ae
Compare
I reported the GitHub Actions ppc64le (and s390x) performance issue IBM/actionspz#38 coming from the wrong CPU settings in the containers. |
80efe5a
to
b437998
Compare
b437998
to
d3a0ca2
Compare
I found the root cause IBM/actionspz#38 (comment). |
ede819f
to
323cfea
Compare
As the issue IBM/actionspz#34 still blocks to add GitHub Actions ppc64le to ruby/ruby, I sent the #14345 to merge only the 1st commit related to the |
570eee4
to
c617b31
Compare
People at IBM said they they fixed the issue IBM/actionspz#34 that jobs sometimes not starting, and I confirmed the GitHub Actions ppc64le/390x jobs started without delay on this PR's latest CI. So, let's merge this PR adding the s390x and ppc64le, and we will see how these work. |
I see my fork repository's CI: https://github.com/junaruga/ruby/actions/runs/17273836937 is failing because there is not cases in the |
20b9a15
to
42b4b2b
Compare
This reverts commit c3c74e0.
* Remove logic that was used for the ubuntu.yml, but not used for ubuntu-ibm.yml. * Add a dummy Ubuntu x86_64 case to make this CI pass on fork repositories. This case only runs on fork repositories.
Note that the default configure option `./configure cppflags=-DRUBY_DEBUG` with the default optimization level `-O3`, causes the following Ractor test and other tests failing. So, we don't set the option in ppc64le case. ``` $ make btest BTESTS=bootstraptest/test_ractor.rb ``` See https://bugs.ruby-lang.org/issues/21534 for details.
42b4b2b
to
afca9c4
Compare
Note that the default configure option
./configure cppflags=-DRUBY_DEBUG
causes the following Ractor test and other tests failing. So, we don't set the
option in ppc64le cases.
You can check the following ticket for details.
https://bugs.ruby-lang.org/issues/21534