| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This reverts commit e8124729fbeaf159ae615f61980ee10018ed5134.
It worked once, but soon after that it stopped working again
https://travis-ci.org/ruby/ruby/jobs/598491972
|
| |
|
|
|
|
|
|
|
| |
Follow up https://github.com/ruby/ruby/pull/2559
According to experiments in https://github.com/ruby/ruby/pull/2560,
disabling cache seems to make arm64 build succeed.
|
| |
|
| |
|
|
|
|
|
|
|
| |
and let RUBY_DEBUG=1 job test it.
We usually don't use --jit-debug and we should test no --jit-debug by
default.
|
|
|
| |
misc-16234
|
|
|
|
| |
Isn't it there? http://rubies.travis-ci.org/
|
| |
|
| |
|
| |
|
|
|
|
| |
In 91aa8bfff8, my understanding of the branch was inverted.
|
|
|
|
|
|
|
|
|
|
|
|
| |
For some reason, the Travis osx environment has been really unstable.
It failed on today's cron too:
https://travis-ci.org/ruby/ruby/builds/579843163
As we have almost the same test environment (including OpenSSL version)
in GitHub Actions and it seems to be more stable and faster, I think
there's no motivation to maintain Travis osx CI environment.
By removing this, we'd be able to simplify .travis.yml as well.
|
|
|
|
|
| |
travis-ci user does not live in #ruby-ja. Therefore the notification
isn't working anymore.
|
|
|
|
| |
We don't have topic branches on ruby.git anymore.
|
|
|
|
| |
It looks like a flag which cannot be enabled on configure.
|
| |
|
|
|
|
|
|
|
|
| |
which are usually optimized away by -O3.
This CI can detect missing exports like
ea84a680755b5a7fa700618cbe78e3b2fc7be01d which was needed for
761346a9604ca2c79777d1d67fb5dcc3c30dbf69.
|
|
|
|
|
|
| |
8897fa60fdbc83f9cce7df384893e902c17c1bf2 worked.
But we want to retry that part and this commit is trying to fix the
problem.
|
|
|
|
|
|
| |
58a373e9ed54556e18a13825dfe72d3f7a86b833 and
3868df83330bb897be996604df3862639abbf002
didn't work.
|
|
|
|
| |
https://travis-ci.org/ruby/ruby/jobs/579116510
|
|
|
|
| |
https://travis-ci.org/ruby/ruby/jobs/579108692
|
| |
|
|
|
|
|
| |
Some CIs report to two channels, and some others report to only one.
This makes it consistent. Only alert channel should be alerted.
|
|
|
|
|
|
|
| |
because it has often hanged like
https://travis-ci.org/ruby/ruby/jobs/573691637,
and we also have almost the same test suite on GitHub Actions now, which
seems to be stable in `make check` so far.
|
|
|
|
| |
to clarify what's running for every commit.
|
| |
|
|
|
|
| |
to propagate exit status to travis_retry properly.
|
|
|
|
|
|
| |
anyway we don't need authorization here.
Also retry does not seem to work in the original version, so let's
extend this with retries as a separate github action later.
|
|
|
|
|
|
|
|
|
|
| |
because it randomly fails on authorization like:
https://github.com/ruby/ruby/runs/190887455
Also the backoff seems too short. Maybe we need tool/travis_retry.sh for
this too.
Cloning ruby/ruby does not need authorization. We don't need to use
actions/checkout.
|
|
|
|
| |
as we dropped -v.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not using official travis_retry.bash, because it's not supporting to
modify backoff seconds.
https://github.com/travis-ci/travis-build/blob/0ad8f1886b2c31994d847e126dc5842b7b3513e3/lib/travis/build/bash/travis_retry.bash
Not using official `travis_apt_get_update` function because it does not
propagate exit status to be used by retries.
https://github.com/travis-ci/travis-build/blob/0ad8f1886b2c31994d847e126dc5842b7b3513e3/lib/travis/build/bash/travis_apt_get_update.bash
Co-Authored-By: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
|
|
| |
Co-Authored-By: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 614c90fe21cf1d9cf6fb18684187d8c7e2f61de6, I assumed
apt-add-repository has been stable recently, but I saw PR randomly
failed for it today.
This commit only deals with "ubuntu-toolchain-r-test" and does NOT deal
with `llvm-toolchain-xenial-8` intentionally, because what it does
(mainly curl from build.travis-ci.org) seems to be more reliable than
"ubuntu-toolchain-r-test". Also `&clang-8` jobs are basically
allow_failures and it's less important to be stabilized.
|
|
|
|
|
|
|
|
| |
as it failed https://travis-ci.org/ruby/ruby/jobs/567942969, unlike my
fork CI.
This just rollbacks a minor change in
798474deaf10dbea70c02724b5acf4487bbed660.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
because Travis team does not do it for us:
https://github.com/travis-ci/travis-build/pull/1712
The retried part has failed often even in one day:
https://travis-ci.org/ruby/ruby/jobs/567802384
https://travis-ci.org/ruby/ruby/jobs/567802388
https://travis-ci.org/ruby/ruby/jobs/567695879
https://travis-ci.org/ruby/ruby/jobs/567666931
For doing it easily, this also changes major aliases to
compiler-specific ones, because partially updating `before_install`
logic using `env` key was too hard and we needed to directly write
`before_install` for each package set. As a bonus of it, it may also
skip installing unnecessary packages when just `os: linux` is needed.
I'll revert this if this patch does not contribute to stabilize CI.
|
| |
|
|
|
|
| |
to control erros on our own.
|
|
|
|
|
|
|
| |
This reverts commit e05f397f08e98fb170e3aca885d6028b344e833c.
Failed... https://travis-ci.org/ruby/ruby/jobs/566961111
We should talk to Travis people instead...
|
|
|
|
|
| |
It contains too old configuration that is autorequire. It will be
removed at the RubyGems 3.1.0.
|
|
|
|
|
| |
I forgot to amend again... Details are explained in
f6a6b21f09b24955a44622e1767bf5b6630525be
|
|
|
|
|
|
|
|
|
| |
and thus it does not work with `-v` for investigating hangs well.
This seems to be by design: https://github.com/travis-ci/travis-ci/issues/4190
Also I simplified a comment about `homebrew.update`.
I had this in-flight change while editing e05f397f08e98fb170e3aca885d6028b344e833c
but forgot to ammend this.
|
|
|
|
|
|
|
|
| |
No `brew update` causes "Error: Your Homebrew is outdated" like https://travis-ci.org/ruby/ruby/jobs/547485832,
but doing `brew update` is also problematic like https://travis-ci.org/ruby/ruby/jobs/564916879.
Hoping that the former case is more rare, let's try no `brew update`
again.
|
|
|
|
|
| |
Formerly we did f432fd6ea595ef854e15d6dd65ef0ccb24a70456, but it did not
eliminate our problems: https://travis-ci.org/ruby/ruby/jobs/564804923
|