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

skip -v spec on MJIT

2021-12-18T16:07:02+00:00

fix this failure:

```
configure ... cppflags=-DMJIT_FORCE_ENABLE
...
make test-spec

1)
The -v command line option when used alone prints version and ends FAILED
Expected
"ruby 3.1.0dev (2021-12-18T10:10:42Z master 78c175280b) +MJIT [x86_64-linux]
"
to include "ruby 3.1.0dev (2021-12-18T10:10:42Z master 78c175280b) [x86_64-linux]"
/tmp/ruby/v3/src/trunk-mjit-wait/spec/ruby/command_line/dash_v_spec.rb:9:in `block (3 levels) in '
/tmp/ruby/v3/src/trunk-mjit-wait/spec/ruby/command_line/dash_v_spec.rb:4:in `'
```

http://ci.rvm.jp/results/trunk-mjit-wait@phosphorus-docker/3759943

Rename ::YJIT to RubyVM::YJIT

2021-10-28T17:43:02+00:00

Since the YJIT Ruby module is CRuby specific and not meant for general
use, it should live under RubyVM instead of at top level.

Fix tests with cppflags=-DYJIT_FORCE_ENABLE

2021-10-21T03:52:21+00:00

https://github.com/ko1/build-ruby/commit/0dbd95c6250594b6ddadc3c4424b071704083187

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