From 5e09125581063b2ae8e72c1597e10e3516c568f1 Mon Sep 17 00:00:00 2001 From: k0kubun Date: Thu, 8 Feb 2018 13:56:32 +0000 Subject: 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 --- test/ruby/test_jit.rb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'test') 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) -- cgit v1.2.3