| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The related extensions have been removed.
Related: https://github.com/ruby/ruby/pull/4619
|
| |
|
|
|
|
|
| |
Run only checks for source code. Currently, our CIs do almost
nothing about the documents.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
This reverts commit 10d2341640c57544ca81bd21cfa60a6aff015692.
TravisCI clones the head of the target branch, and it may not be
the target commit at that time.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It seems the concurrent jobs are stable recently on arm64 pipeline.
Keep allowing to fail on arm32 due to a failure.
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
| |
Some certificates on Unicode.org have expired.
|
|
|
|
| |
It was fixed at fc832ffbfaf581ff63ef40dc3f4ec5c8ff39aae6 .
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
| |
This is a LTS. Must be better than Xenial.
|
|
|
|
| |
This reverts commit 6b978d542704a5614af5e9375c4b31b8d2618652.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Is already covered by Github Actions.
|
|
|
|
| |
They were not working.
|
|
|
|
| |
Translate a part of .travis.yml into a Github Actions workflow.
|
|
|
|
| |
Translate a part of .travis.yml into GitHub Actions workflow.
|
|
|
|
| |
These tests are (more or less) covered by github actions now.
|
|
|
|
|
| |
It seems `clang --save-temps` does not interface well with
tool/update-deps. Prefer gcc for that purpose.
|
|
|
|
|
| |
Also install external libraries only, extract-gems does not work
unless base ruby is available.
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
According to warnings on Travis, there's no such key. We handle this on
webhook side anyway.
|
|
|
|
|
| |
This reverts commit 4a6571dbc14ee4e88c12cd9931f7695077a3ee6e,
because chkbuild does not follow.
|
| |
|
| |
|
|
|
|
|
| |
It seems the issue was fixed by Travis.
See https://travis-ci.community/t/6719/5 .
|
|
|
|
| |
Ditto for a833eb29f7eaced61919b7ed19e830a3905e8a8b
|
|
|
|
|
|
| |
It seems fragile now, seemingly due to environmental issues. Lets allow
it to fail for a while. Reported by Jun Agura <jaruga@redhat.com>
[ruby-core:97540]
|
|
|
|
| |
All Slack alerts have been migrated to a bot made by mame-san
|
| |
|
|
|
|
| |
They were necessary when developing YAMLs, but not useful any longer.
|
| |
|
|
|
|
| |
It seems UBSAN is quite stable now.
|
|
|
|
|
| |
Darwin is no longer tested using Travis CI. See also commit
91aa8bfff8a9f9c0af96915c120d863fc474e8d5
|
| |
|
|
|
|
|
|
| |
* With keyword argument changes, it's more likely to break only 2.7 and
not other versions.
* A few specs were broken on 2.7.0 recently, this should catch them earlier.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This fixes following error that sometimes happens once in a few times
on Travis s390x environment.
```
$ tool/travis_retry.sh sudo -E apt-add-repository -y "ppa:ubuntu-toolchain-r/test"
+ sudo -E apt-add-repository -y ppa:ubuntu-toolchain-r/test
Error: retrieving gpg key timed out.
```
|
|
|
|
|
| |
We don't find it useful anymore, because notifications from many other
CIs are mixed.
|