summaryrefslogtreecommitdiff
path: root/.travis.yml
AgeCommit message (Collapse)Author
2023-11-10.travis.yml: Run arm64 without allow_failiures.Jun Aruga
Checking the past 10 builds in Travis CI arm64, it looks stable. So, disable `allow_failures`. Also sorted the order of the jobs for the priority. The arm64 is the first. And I would like to run arm32 using the arm64 pipeline a bit later after the arm64 using the same arm64 pipeline. So, the arm32 is the last.
2023-11-09.travis.yml: Add arm64 case.Jun Aruga
In the past, I saw that the 2nd arm64 pipeline was unstable. Now I want to try it to check if it is stable enough to run again. As far as I know, right now the only native arm64 cases are MacOS Arm `macos-arm-oss` on GitHub Actions. And I want to add Linux arm64 case on pull-request in CI.
2023-11-03.travis.yml: Add a RubyGems issue ticket link.Jun Aruga
Add a RubyGems issue ticket link. The issue happend in Travis arm32 at once.
2023-11-03.travis.yml: Add Ruby and RubyGems version info.Jun Aruga
The version information is useful to report issues to Ruby and RubyGems projects.
2023-11-03.travis.yml: s390x: Use GCC 11.4.0.Jun Aruga
Use GCC version 11.4.0 (gcc-11 package) instead of the default GCC 11.3.0 to align with the GCC used in the RubyCI s390x server below. ``` $ /usr/bin/gcc --version gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 Copyright (C) 2021 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ ls -l /usr/bin/gcc lrwxrwxrwx 1 root root 6 Aug 5 2021 /usr/bin/gcc -> gcc-11* $ dpkg -S /usr/bin/gcc-11 gcc-11: /usr/bin/gcc-11 ``` Ubuntu Jammy gcc-11: https://packages.ubuntu.com/jammy-updates/gcc-11
2023-11-03.travis.yml: Reduce the parallel job number.Jun Aruga
I think the "1+$(nproc)" is too much.
2023-11-03.travis.yml: Disable ppc64le allow_failures.Jun Aruga
Now I expect that Travis ppc64le always passes without any random failures by the commit 1f1b9b0942ec12dde1af8000f8cb84692904fccc that is a workaround to pass the `test/rdoc/test_rdoc_generator_json_index.rb` in Travis ppc64le case.
2023-10-30.travis.yml: Refactor.Jun Aruga
* 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.
2023-10-30.travis.yml: Disable s390x allow_failures.Jun Aruga
To avoid unintentional new failures. Feel free to enable it again when the case is unstable.
2023-10-30.travis.yml: Remove optflags=-O1 except arm32.Jun Aruga
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
2023-10-30.travis.yml: Upgrade the Ubuntu ppc64le to 22.04 (Jammy).Jun Aruga
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.
2023-10-28Revert ".travis.yml: Drop s390x temporarily." (#8792)Jun Aruga
It seems the Travis s390x is recovered again now. This reverts commit 95cc0f946eb641be8dea4b7118598be77d993183.
2023-10-27.travis.yml: Disable allow_failures for arm32.Jun Aruga
I want to disable allow_failures if possible to avoid unintentional new failures. It seems that the arm32 case is stable. Feel free to enable allow_failures again when you see the case is unstable.
2023-10-27.travis.yml: Upgrade the Ubuntu arm32 to 22.04 (Jammy).Jun Aruga
Upgrade the gcc version to the latest version 11.4.0 to align the gcc version used in the RubyCI arm64 server.
2023-10-27.travis.yml: Drop s390x temporarily.Jun Aruga
The s390x pipeline is unstable with the error "No output has been received" or doesn't start. See <https://travis-ci.community/t/13811>.
2023-10-27.travis.yml: Simplify Travis CI.Jun Aruga
* Remove CI functions for make test-all. I want to simplify the `.travis.yml` for us to maintain it easily. When we need to skip a test, we can fix the test file directly. I removed the `tool/ci_functions.sh` too. I confirmed the file is not used in any other files. * .travis.yml: Remove a notification for IRC channel. GitHub Actions don't use this notification. The setting is outdated. * Fix to skip the commit including the document keyword. There were 2 `if` syntax lines in the file. * Remove ccache.
2023-09-29.travis.yml: Upgrade the used Ubuntu s390x to 22.04 (Jammy). (#8401)Jun Aruga
Upgrade the used Ubuntu version from 20.04 (Focal) to 22.04 (Jammy), alignin with RubyCI "s390x (Ubuntu)" server. https://rubyci.org/ Note Travis CI supports Ubuntu 22.04 (Jammy). https://docs.travis-ci.com/user/reference/jammy/ Set `DFLTCC=0` environment variable as a workaround to avoid the test failures related to zlib in the `make test-all` and `make test-spec`. The failures can happen with the zlib library applying the patch madler/zlib#410 to enable the deflate algorithm producing a different compressed byte stream.
2023-09-08Try default `gcc` 9.4.0 to see if it exhibits the same compiler bugs. (#8394)Samuel Williams
* Revert "Extract `do_mutex_lock_check_interrupts` to try and fix `ppc64le`. (#8393)" This reverts commit 5184b40dd4dc446660cd35c3e53896324e95b317. * .travis.yml: Try default gcc 9.4.0 instead of gcc-10 in ppc64le and s390x. Use gcc 9.4.0 instead of gcc-10 to avoid the current failures by a possible GCC 10 compiler bug in the Travis ppc64le and s390x cases. And it also aligns with RubyCI Ubuntu ppc64le and s390x where the default gcc is used. --------- Co-authored-by: Jun Aruga <jaruga@ruby-lang.org> Notes: Merged-By: ioquatix <samuel@codeotaku.com>
2023-08-12Use the default test-spec formatter on TravisNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/8210
2023-07-02[Travis] make `.bundle` directory writableNobuyoshi Nakada
To create gem files from sources under `gems/src` for tests. Notes: Merged: https://github.com/ruby/ruby/pull/8012
2022-09-15[TravisCI] The source of YAML is no longer bundledNobuyoshi Nakada
2022-09-15[TravisCI] Make gems/src directory writableNobuyoshi Nakada
2022-06-19Skip CIs if the head commit message contains '[DOC]'Nobuyoshi Nakada
2022-03-04Remove gdbm related code from Travis CIKazuhiro NISHIYAMA
The related extensions have been removed. Related: https://github.com/ruby/ruby/pull/4619
2021-12-21Ignore hung-ups after success on s390x-linux tentatively [ci skip]Nobuyoshi Nakada
2021-12-16[DOC] Skip tests if only documents change [ci skip]Nobuyoshi Nakada
Run only checks for source code. Currently, our CIs do almost nothing about the documents.
2021-10-20Reduce the amount of false positive notificationsTakashi Kokubun
While f6048e592c520e20ba498ba4d553f07f02213a61 tried to approach the instability mentioned there, unfortunately the Travis arm32 environment seems unstable by itself. I already saw 2 different failures in the last 4 builds: https://app.travis-ci.com/github/ruby/ruby/jobs/544382885 https://app.travis-ci.com/github/ruby/ruby/jobs/544361370 Let's revisit this when this kind of thing stops happening.
2021-10-13Revert "Shallow clone on TravisCI"Nobuyoshi Nakada
This reverts commit 10d2341640c57544ca81bd21cfa60a6aff015692. TravisCI clones the head of the target branch, and it may not be the target commit at that time.
2021-10-13Shallow clone on TravisCINobuyoshi Nakada
2021-10-12.travis.yml: Comment out the 2nd arm64 pipeline.Jun Aruga
The 2nd arm64 pipeline is unstable now in Travis. As Cirrus CI has arm64 pipelines, it's not a problem to drop the arm64 pipeline in Travis. Notes: Merged: https://github.com/ruby/ruby/pull/4956
2021-10-10Run the failing readline test on arm32-linux separatelyNobuyoshi Nakada
2021-10-10Remove `RUN_SEPARATED_TESTS` which seems unnecessaryNobuyoshi Nakada
2021-10-10Set `TEST_ALL` options first to show in the summary pageNobuyoshi Nakada
2021-08-13Reduce the amount of false positive notificationsTakashi Kokubun
2021-08-09.travis.yml: Check failures for Travis arm64 again.Jun Aruga
It seems the concurrent jobs are stable recently on arm64 pipeline. Keep allowing to fail on arm32 due to a failure. Notes: Merged: https://github.com/ruby/ruby/pull/4726
2021-06-09Enable Travis on the specific branches or forked repositories.Jun Aruga
Align the Travis enabling timing with GitHub Actions. For the syntax, see <https://docs.travis-ci.com/user/conditions-v1>. We use `repo` syntax rather than `fork = true/false` syntax to show a general usage in any repositories on GitHub. The non-forked repo is not always a primary repo in any GitHub repositories. [Bug #17936] Notes: Merged: https://github.com/ruby/ruby/pull/4556
2021-06-07Get rid of updating Unicode filesNobuyoshi Nakada
Some certificates on Unicode.org have expired.
2021-05-26.travis.yml: Remove skipped tests on ppc64le.Jun Aruga
It was fixed at fc832ffbfaf581ff63ef40dc3f4ec5c8ff39aae6 . Notes: Merged: https://github.com/ruby/ruby/pull/4529
2021-05-25.travis.yml: Update to use arm64/ppc64le/s390x.Jun Aruga
* Use only the free pipelines arm64/ppc64le/s390x without credits on Travis. See <https://docs.travis-ci.com/user/billing-overview/#partner-queue-solution>. * Add ppc64le case. * Update the gcc to gcc-11. * Remove unused logic. * Add the `tool/travis_wait.sh` to avoid a command timeout. * Run the tests skipping some failing tests. * Set `TEST_ALL_SKIPPED_TESTS` env to skip the tests. * Run the tests separately returning ok status. The tests are executed if `TEST_ALL_SKIPPED_TESTS` env is set or `TEST_ALL_SEPARATED_TESTS` env is set. * Add `tool/ci_functions.sh` to manage the functions used in CI. * Add arm64 to allow_failures due to the following issue. An arm64 job sometimes does not start right now. https://travis-ci.community/t/11629 Notes: Merged: https://github.com/ruby/ruby/pull/4518
2021-05-25.travis.yml: Ubuntu 20.04 Focal Fossa卜部昌平
This is a LTS. Must be better than Xenial. Notes: Merged: https://github.com/ruby/ruby/pull/4518
2021-05-25Revert "Remove .travis.yml" to revive Travis.Jun Aruga
This reverts commit 6b978d542704a5614af5e9375c4b31b8d2618652. Notes: Merged: https://github.com/ruby/ruby/pull/4518
2021-03-12Remove .travis.ymlNARUSE, Yui
Reason: * Recent build is failed. https://travis-ci.org/github/ruby/ruby/jobs/762561190 * Current configuration uses Ubuntu 16.04 (xenial), whose EOL is Apr 2021. If someone want to recover Travis CI builds, please fix above two issues.
2020-11-04.travis.yml: delete x86_64卜部昌平
Is already covered by Github Actions. Notes: Merged: https://github.com/ruby/ruby/pull/3731
2020-11-04.travis.yml: delete sanitizer tests卜部昌平
They were not working. Notes: Merged: https://github.com/ruby/ruby/pull/3731
2020-11-04.github/workflows/baseruby.yml: add卜部昌平
Translate a part of .travis.yml into a Github Actions workflow. Notes: Merged: https://github.com/ruby/ruby/pull/3731
2020-10-23.github/workflows/spec_guards.yml add卜部昌平
Translate a part of .travis.yml into GitHub Actions workflow. Notes: Merged: https://github.com/ruby/ruby/pull/3685
2020-10-21.travis.yml: reduce redundant tests卜部昌平
These tests are (more or less) covered by github actions now. Notes: Merged: https://github.com/ruby/ruby/pull/3675
2020-08-22.travis.yml: prefer gcc卜部昌平
It seems `clang --save-temps` does not interface well with tool/update-deps. Prefer gcc for that purpose.
2020-06-16Just update sources in CI without fetchingNobuyoshi Nakada
Also install external libraries only, extract-gems does not work unless base ruby is available.
2020-05-03Travis s390x-linux is too unstableTakashi Kokubun
It has caused errors by ENOSPC like https://travis-ci.org/github/ruby/ruby/jobs/682520961 too often. I cleared all cache of Travis yesterday, but it didn't help it. Until somebody figures out how to fix it, let me exclude it from CI status reports to avoid false alerts.