-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
.travis.yml: Upgrade the Ubuntu ppc64le to 22.04 (Jammy). #8739
Conversation
It seems when I did |
af2dd0e
to
da095e1
Compare
I am adding the 3rd commit to pass the This commit causes the
|
I noticed that Travis ppc64le jammy gcc version is 11.3.0, while RubyCI ppc64le server's gcc version is 11.4.0. I will upgrade Travis ppc64le's gcc version. I suppose this fixes the current stucking |
I noticed that the RubyCI ppc64le server's gcc is forcely symbolic linked to the gcc-11 deb package. https://packages.ubuntu.com/jammy-updates/gcc-11
|
Here is the result of Ubuntu jammy s390x server. The gcc-11 is also used as a default gcc.
|
And the default gcc is also gcc-11 on the Ubuntu jammy arm64 server too.
|
4fa5e68
to
e4beaa2
Compare
I see the https://app.travis-ci.com/github/ruby/ruby/jobs/612123590#L3101
|
First I want to simplify the |
e4beaa2
to
dd07303
Compare
First, I want to upgrade only arm32 case on another PR #8790 . Then I will come back to this PR. I still see the following issue on Ubuntu jammy ppc64le, and GCC 11.4.0.
|
dd07303
to
f5cec69
Compare
f5cec69
to
5f625f2
Compare
Seeing the recent successes on RubyCI ppc64le Ubuntu jammy servers, it's time to upgrade Travis ppc64le to jammy. http://rubyci.s3.amazonaws.com/ppc64le/ruby-master/recent.html Upgrade the gcc version to the latest version 11.4.0 to align the gcc version used in the RubyCI ppc64le server's gcc version.
5f625f2
to
3d3e24e
Compare
We want to align the used build flags with RubyCI ppc64le Ubuntu jammy server as much as possible to avoid Travis specific issues. Still keep the -O1 for only arm32 due to the following issue. https://bugs.ruby-lang.org/issues/19981
To avoid unintentional new failures. Feel free to enable it again when the case is unstable.
* Add notes. * When you see Travis issue, please check the link below. https://github.com/ruby/ruby/wiki/CI-Servers#travis-ci * Added the following random failure. The ppc64le failure has been happening randomly in Travis focal/jammy. TestRDocGeneratorJsonIndex#test_generate fails randomly. https://app.travis-ci.com/github/ruby/ruby/jobs/612380961#L2900 * Update the comments. * Remove empty lines in nested YAML elements aligning with other parts.
6550445
to
66813ed
Compare
It seems that the |
This PR is to upgrade Travis Ubuntu ppc64le to 22.04 (jammy). Seeing the recent successes on RubyCI ppc64le Ubuntu jammy server, it's time to
change Travis ppc64le to jammy.
http://rubyci.s3.amazonaws.com/ppc64le/ruby-master/recent.html
It seems that the all the Travis cases are failing right now after the commit 9e93af5 .
https://app.travis-ci.com/github/ruby/ruby/builds/266750115
I also plan to disable
allow-allow_failures
if the Travis CI is stable enough for that, to avoid unintentional new failures.