k0kubun	2018-02-08 22:56:32 +0900 (Thu, 08 Feb 2018)

  New Revision: 62314

  https://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=62314

  Log:
    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

  Modified files:
    trunk/test/ruby/test_jit.rb
Index: test/ruby/test_jit.rb
===================================================================
--- test/ruby/test_jit.rb	(revision 62313)
+++ test/ruby/test_jit.rb	(revision 62314)
@@ -11,6 +11,8 @@ class TestJIT < Test::Unit::TestCase https://github.com/ruby/ruby/blob/trunk/test/ruby/test_jit.rb#L11
   ]
 
   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 https://github.com/ruby/ruby/blob/trunk/test/ruby/test_jit.rb#L58
     "```\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)
 

--
ML: ruby-changes@q...
Info: http://www.atdot.net/~ko1/quickml/