Unaligned word access warnings generated by UBSAN are often
treated well already, depending on this macro.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65593 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
I remember this configuration unveiled several bugs before.
Better check it occasionally.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65559 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Inspired by [GH-1984], let us add some tests that run only
once a day. These configurations are either slow to compile
or slow to run. But I think they are worth done occasionally.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65556 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Seems it is failing to compile right now; make it mandatory
so that other devs can be aware of it.
Will revert this change once the source code gets stable.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65462 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
It looks like mspec worker may immediately die on Linux as well.
https://travis-ci.org/ruby/ruby/jobs/447018758
Dropping -j and add -fs to know which test dies.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65386 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
to shorten time taken for finishing overall builds.
appveyor.yml: comment the same intention in AppVeyor as well
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65328 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
because it may hang with no output like this:
https://travis-ci.org/ruby/ruby/jobs/445101860
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65326 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
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
-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
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
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
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
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
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
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
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
* .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
* .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
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
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
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
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
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
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
k0kubun
shyouhei
eregon
nobu
kazu
hsbt