Age | Commit message (Collapse) | Author |
|
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
|
|
I think it's been stable these days.
|
|
Set osx_image under each configuration, as it decides the OS (and
kernel) version not only Xcode version, and the configuration name
contains the kernel version.
|
|
but shorten --timeout-scale for now to avoid finishing with timeout
if possible.
timeout: https://travis-ci.org/ruby/ruby/jobs/564370175
|
|
for failures like https://travis-ci.org/ruby/ruby/jobs/564351066
|
|
Also Homebrew is up-to-date and "Updating Homebrew" takes less
than one minute.
|
|
|
|
|
|
|
|
because it failed again https://travis-ci.org/ruby/ruby/jobs/563026412
even after 676df311d90990a4666adb5b1db4c7aa6b080e57.
|
|
Often checked out files are in the future on OSX image.
|
|
[ci skip]
|
|
|
|
|
|
Even after 19d592dc82a31adf0bb6f027392cae69615c2394, the retry seems not
functional. Let's just add --debug from the beginning because an output
of each step is collapsed and we don't see `make up` output so often.
|
|
|
|
|
|
|
|
nobu said that we could be banned if we aggressively downloaded unicode
file from Travis.
|
|
|
|
|
|
|
|
https://travis-ci.org/ruby/ruby/jobs/553346285
|
|
and now Travis should run on master, instead of trunk.
(this is testing git push to master branch)
|
|
Eregon did not want https://github.com/ruby/ruby/commit/7b9dd379bfe4d597acfe4c26365feff61dabd488
because people only see Travis job name and don't see .travis.yml.
I believe the new job name is simple and informative enough to explain
why it exists.
|
|
|
|
because Travis is crashing like "Error: Your Homebrew is outdated.
Please run `brew update`."
https://travis-ci.org/ruby/ruby/jobs/547485832
|
|
|
|
|
|
This reverts commits:
* 6f9d5fafe040cb02a1278fbfcdcb8063d564824c
* bb3c89b6437049e26669b2156310670d5e06e386
And remove the dependency of Makefile on Makefile.in
transitionally.
|
|
|
|
|
|
We have no clear assertion or check of BASERUBY requirement.
I want to make the current situation more explicit.
I'm NOT saying we should support Ruby 1.9.3 here,
but I'm just checking the situation as per 05bc14d81a1d7f6af826a92371aeff0c3fb2a67e.
FYI, at this moment Ruby 1.8.7 did not work with this Travis config, like:
https://travis-ci.org/k0kubun/ruby/builds/538459100
|
|
This has been unused since b7f5c573ef20dbbf5534ee3a45625c7f9d45f2ec.
|
|
but on "master" branch.
For Pull Request, I changed the approach from
d9b338a53f520b2dbb05555f18b8de8072300f40 and
277e68825a8e4d0e6503a32e41f8b1b6c078b567.
|
|
|
|
|
|
Sanitizers and fortifications do not interface, and there is currently
no plan for them to work together.
See also https://github.com/google/sanitizers/issues/247
|