ruby.git/test/excludes/_wercker, branch master

Migrate Wercker MJIT tests to Actions (#2676)

2019-11-13T05:48:05+00:00

* Migrate Wercker MJIT tests to Actions

* Support pull request for testing

* Capitalize other jobs too

* Make it a command name for consistency [ci skip]

* Remove wercker.yml

* Add --jit-verbose=2 for debugging

* Install MJIT headers

* Separate install for sudo

* Trigger build

Test GC.compact on MJIT again

2019-05-23T07:07:16+00:00

Isolate TestGCCompact from JIT testing

2019-04-27T03:28:52+00:00

Wercker seems to randomly fail
https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cc3c1c423fcb70008db9b64?step=5cc3c46a03f4460007da0659

To help debugging, let me isolate the impact from GC.compact in the JIT
testing on Wercker.

test/excludes/_wercker: give up testing TestGemRemoteFetcher

2018-12-21T14:33:25+00:00

The tests are really fragile with --jit-wait and it doesn't have interface
to modify this timeout at all.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66480 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

test/excludes/_wercker: remove obsoleted pipeline name

2018-11-16T06:52:12+00:00

from excludes directory names. test-mjit-wait / test-mjit are combined
and distributed as mjit-test1 and mjit-test2 now.

So the subdirectory names are changed to option names, --jit and --jit-wait.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65766 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

TestDelegateClass.rb: skip test_frozen for --jit-wait

2018-11-01T07:49:06+00:00

for now. Investigating.
https://app.wercker.com/ruby/ruby/runs/mjit-test2/5bda979a191eda000655a8d2?step=5bda9fe4591ca80007653f64

wercker.yml: improve parallelism again.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65489 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

_mjit_compile_ivar.erb: cancel on undefined ivar

2018-10-24T15:41:14+00:00

I assumed somehow this check was not needed, but it did need.
By canceling this instead of just warning here, we didn't lose the
current performance so much.

test_jit.rb: test the case that reproduces SEGV by that.

TestGemStreamUI.rb: delete. This test on --jit-wait is fixed.

=== Optcarrot Benchmark ===

$ benchmark-driver benchmark.yml --rbenv 'before::before --disable-gems --jit;after::after --disable-gems --jit' -v --repeat-count 24
before: ruby 2.6.0dev (2018-10-24 trunk 65355) +JIT [x86_64-linux]
after: ruby 2.6.0dev (2018-10-24 trunk 65355) +JIT [x86_64-linux]
last_commit=_mjit_compile_ivar.erb: cancel on undefined ivar
Calculating -------------------------------------
                             before       after
Optcarrot Lan_Master.nes     85.344      84.849 fps

Comparison:
             Optcarrot Lan_Master.nes
                  before:        85.3 fps
                   after:        84.8 fps - 1.01x  slower

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65356 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

test/excludes/_wercker: skip tests

2018-10-24T12:13:28+00:00

which are under investigation. I'm debugging it right now, but let's
make it green to stop bothering other development.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65351 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

wercker.yml: skip TestParallel::TestParallel#test_separate

2018-10-24T10:29:39+00:00

for now. It's randomly failing on test-mjit-wait.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65348 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

wercker.yml: skip test_queue_with_trap on -wait as well

2018-10-24T03:05:43+00:00

It randomly failed.
https://app.wercker.com/ruby/ruby/runs/test-mjit-wait/5bcfd19aa9806e000655c598?step=5bcfd1d5acc4510006e00f77

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65346 b2dd03c8-39d4-4d8f-98ff-823fe69b080e