summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-02-08 13:56:32 +0000
committerk0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-02-08 13:56:32 +0000
commit5e09125581063b2ae8e72c1597e10e3516c568f1 (patch)
treed0d5a4b2d513e8172657389d3496dd7cbc90e494
parent288b44328dbd22429eaaed5243d7bea8a3116016 (diff)
test_jit.rb: don't force to test --jit-wait
for platforms which can't use JIT. Such platforms can time out with eval_with_jit. http://ci.rvm.jp/results/trunk_gcc5@silicon-docker/509911 http://ci.rvm.jp/results/trunk_gcc4@silicon-docker/509904 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62314 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-rw-r--r--test/ruby/test_jit.rb4
1 files changed, 2 insertions, 2 deletions
diff --git a/test/ruby/test_jit.rb b/test/ruby/test_jit.rb
index 71807c5eba..f519f72059 100644
--- a/test/ruby/test_jit.rb
+++ b/test/ruby/test_jit.rb
@@ -11,6 +11,8 @@ class TestJIT < Test::Unit::TestCase
]
def test_jit
+ skip unless jit_supported?
+
assert_eval_with_jit('print proc { 1 + 1 }.call', stdout: '2', success_count: 1)
end
@@ -56,8 +58,6 @@ class TestJIT < Test::Unit::TestCase
"```\n#{code}\n```\n\n"
end
- # If this is false, tests which require JIT should be skipped.
- # When this is not checked, probably the test expects Ruby to behave in the same way even if JIT is not supported.
def jit_supported?
return @jit_supported if defined?(@jit_supported)