summaryrefslogtreecommitdiff
path: root/.travis.yml
AgeCommit message (Collapse)Author
2018-10-21Exclude CI platform specific failures by --excludes optionnobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65265 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-21.travis.yml: mspec -j is unstablek0kubun
https://travis-ci.org/ruby/ruby/jobs/444232677 Instead of that, add -fs to know problematic test case when failed. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65261 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-21.travis.yml: use --job-status=replacek0kubun
-v is too long, and "--color=never --job-status=normal" is too verbose. Trying --job-status=replace to make Travis log easier to read. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65260 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-21.travis.yml: debug problematic test case on osxk0kubun
osx build is stucking somewhere. We want to debug that. https://travis-ci.org/ruby/ruby/jobs/444059226 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65258 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-19.travis.yml: separate apt addons for i686-linuxnobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65181 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-19test/lib/jit_support.rb: fire test_jit everywherek0kubun
That was a workaround to make rubyci green for a short term after the MJIT merge. As we've done many portability fixes for MJIT, let's try running test_jit on all rubyci platforms. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65175 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-19.travis.yml: try promoting osx to non-allow_failuresk0kubun
somehow it gets stable there days... Later, we may be able to add wrapper to apply timeout appropriately and dump threads, in case that it stucks. It's not super easy to write it, so this commit just tries to enable osx for now. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65168 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-19.travis.yml: delete duplicated --disable-install-doc [ci skip]shyouhei
The flag was already specified inside of before_script git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65165 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-19.travis.yml: name each builds [ci-skip]shyouhei
Just cosmetic update. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65164 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-19.travis.yml: add i686-linux testsshyouhei
This is a better-than-nothing compilation check that compiles 32bit binary on a 64bit VM. Commented out are universal.i386-darwin17 biulds, which I think are in very low priority. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65163 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-18.travis.yml: add -pedantic build (2nd try)shyouhei
Now that we have allow_failures, why not add configurations that are prone to fail. The first thing I want to add is $CC -ansi -pedantic, which spots lots of bugs on my local machine. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65153 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-18revert r65151, because the other tests were broken.shyouhei
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65152 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-18.travis.yml: add -pedantic buildshyouhei
Now that we have allow_failures, why not add configurations that are prone to fail. The first thing I want to add is $CC -ansi -pedantic, which spots lots of bugs on my local machine. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65151 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-18.travis.yml: no additional apt packages for spec/ruby [ci skip]nobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65147 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-18.travis.yml: should escape spacesshyouhei
workarounds for https://github.com/travis-ci/travis-ci/issues/1444 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65146 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-18.travis.yml: just use envshyouhei
You don't have to use `before_install` to introduce new environment variables; that is to be done using `env` command. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65145 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-18.travis.yml: no PR in spec/ruby [ci skip]nobu
* .travis.yml (before_script): spec/ruby has been incorporated already, no pull-requests to merge. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65144 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-18.travis.yml: fix typo in configure argumentsshyouhei
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65143 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-18.travis.yml: split before_install into the matrixnobu
* .travis.yml (before_install): split shell commands into the matrix per OSs, so that the commands will appear in the logs separately. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65142 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-17.travis.yml: revert r65131 took0kubun
because it succeeded https://travis-ci.org/ruby/ruby/jobs/442733840. It looks that it randomly succeeds. Let's just leave it and see how stable it is, starting from `allow_failures` because it hasn't hanged only once so far. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65138 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-17revert r65124 and try non-parallel test-all on osxk0kubun
OpenSSL error was fixed but r65124 hanged too https://travis-ci.org/ruby/ruby/jobs/442727035. So it seems to be an independent issue. Let me try removing -j. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65131 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-17.travis.yml: try openssl stable versionk0kubun
macOS build is handing on OpenSSL::SSL::SSLError https://travis-ci.org/ruby/ruby/jobs/442706479 Now 1.0.2p is stable version https://formulae.brew.sh/formula/openssl, so let me try that version to make CI green git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65124 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-17.travis.yml: enhance build matrixshyouhei
add OS=osx compiler=clang build matrix so that we can make sure things are built smoothly on that platform. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65122 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-15.travis.yml: try `addons.apt.config.retries: true` as wellk0kubun
This is suggested by Travis https://github.com/travis-ci/travis-ci/issues/9112#issuecomment-376305909 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65084 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-15.travis.yml: try `addons.apt.update: true` for gcc-8k0kubun
because gcc-8 setup is super unstable like this https://travis-ci.org/ruby/ruby/jobs/441528813 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65083 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-19ruby_2_2 branch has endedkazu
https://www.ruby-lang.org/en/news/2018/06/20/support-of-ruby-2-2-has-ended/ [ci skip] git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64783 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-12.travis.yml: run ruby/spec version guards check in parallelnobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64698 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-12deduce versioned tools from CCnobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64694 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-09.travis.yml: separate ruby/spec on old versionnobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64668 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-09Add latest version gcc-8 case to Travis CInobu
[Fix GH-1937] Co-authored-by: Jun Aruga <jaruga@redhat.com> git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64667 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-09.travis.yml: branches only for travis-cinobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64666 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-21Run specs against 2.3.7 to ensure version guards are correctly addederegon
* See [Feature #15004]. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64502 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-02-11.travis.yml: resurrect notification to #commitsk0kubun
I heard at least Shibata-san sees the channel for the notification. But I want #alets to have all CI failure notifications too. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62361 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-02-11.travis.yml: send notification to #alertsk0kubun
instead of #commits. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62359 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-02-09.travis.yml: force to execute JIT test on Travisk0kubun
test_jit.rb: with environment variable RUBY_FORCE_TEST_JIT, we can force to test JIT availability. I wanted to have such CI, but Travis was the only option which I can modify easily. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62327 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-02-07.travis.yml: try `make install` to test JITk0kubun
If header is not available, JIT won't be tested. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62295 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-01-26Removed workaround Travis CI.hsbt
Revert r61209, r61210 From: SHIBATA Hiroshi <hsbt@ruby-lang.org> git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62048 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-01-05Try to fix Travis CI configuration.hsbt
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61605 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-12-25Add ruby_2_5 branch to .travis.ymlnaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61470 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-12-13Travis: the workaround needs sudo: required to workeregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61210 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-12-13Use the older Travis CI imageeregon
* The new one produces many warnings like: warning: Insecure world writable dir /usr/local/clang-5.0.0/bin in PATH, mode 040777 * Workaround from https://blog.travis-ci.com/2017-12-12-new-trusty-images-q4-launch git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61209 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-11-23.travis.yml: revert "workaround to resolve ::1"k0kubun
This commit reverts r60736. Shibata-san reported the cause of r60736 to Travis and it seems fixed: https://github.com/travis-ci/travis-ci/issues/8780 In another CI, I found "::1 ip6-localhost ip6-loopback" in build system information, unlike "::1 localhost ip6-localhost ip6-loopback" that had failed in Ruby's CI on Travis. Let's try Container-based environment again. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@60886 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-11-10.travis.yml: workaround to resolve ::1k0kubun
Container-based Trusty environment (sudo: false) does not support IPv6. https://github.com/travis-ci/travis-ci/issues/3302 And the image has "::1 localhost ip6-localhost ip6-loopback" entry in addition to "127.0.0.1 localhost" in /etc/hosts. Thus when it can resolve localhost to ::1 and CI fails. To resolve this, at least we need to modify /etc/hosts for now but we can't modify /etc/hosts without sudo. So I enabled sudo. As Sudo-enabled VM didn't have "::1 localhost" entry, this change fixed the cause without touching /etc/hosts. Since boot of `sudo: required` is slower than `sudo: false`, please revert this commit anytime when Container-based Trusty environment is updated and ::1 issue has gone. https://docs.travis-ci.com/user/reference/overview/ git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@60736 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-10-25Regenerate slack token on Travis CI.hsbt
The previous token did not work on our slack team. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@60422 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-09-20Adapt tools to follow spec/rubyspec => spec/ruby renameeregon
* [Misc #13792] [ruby-core:82287] * Prefer test-spec over test-rubyspec in spec/README. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59980 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-09-05Update credentials for Travis/Slack integration.hsbt
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59750 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-08-02Partly reverted email notification on travis configuration.hsbt
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59464 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-08-02Remove "make update-rubyspec"kazu
because it is no-op for compatibility git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59460 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-07-27Update configuration for slack notification.hsbt
* Encrypted slack token. * Only notify when build fails and it recovered. * Only notify trunk build without pull requests. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59429 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-07-26To use slack notification instead of email notification.hsbt
It's easily customize configuration of test notify. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59423 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-19 22:31:30 +0000