ruby.git/spec/ruby/command_line/dash_v_spec.rb, branch v3_0_4

use `should include`.

2018-10-09T06:18:28+00:00

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

spec/ruby: revert r63503 and r63508

2018-05-29T08:46:36+00:00

When RUBY_DESCRIPTION has `+JIT` already, it will be doubled.
Just fake.rb.in always has copied `RUBY_DESCRIPTION`, regardless
MJIT is enabled or not.  `BOOTSTRAPRUBY` is not involved.

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

Specs must keep working on older versions and other implementations

2018-05-27T09:52:04+00:00

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

spec/ruby: fix RUBY_DESCRIPTION check with JIT enabled

2018-05-24T14:32:05+00:00

`make test-spec` adds `-r./$(arch)-fake` to pass header options.
But the $(arch)-fake.rb unexpectedly modifies RUBY_DESCRIPTION and it
always drops +JIT from it since the fake.rb is built with BOOTSTRAPRUBY,
which can be miniruby. miniruby can't find MJIT header and thus
mjit_init_p is always FALSE.

So, to pass `make test-spec` with JIT enabled, we can't use
RUBY_DESCRIPTION.

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

Update to ruby/spec@c1b568b

2018-03-04T15:09:32+00:00

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

Update to ruby/spec@691755d

2017-09-28T09:19:59+00:00

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

Move spec/rubyspec to spec/ruby for consistency

2017-09-20T20:18:52+00:00

* Other ruby implementations use the spec/ruby directory.
  [Misc #13792] [ruby-core:82287]

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