|author||k0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>||2018-10-22 15:49:22 +0000|
|committer||k0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>||2018-10-22 15:49:22 +0000|
revisit more MJIT test skips
r65308 passed both trunk-mjit and trunk-mjit-wait CIs. MJIT copy job looks working fine. Then this commit skips 5 more tests. Some of them were skipped in a very early stage and may still need to be skipped, but I want to confirm them since they haven't been changed for a long time. And this prefers having inline information on `RubyVM::MJIT.enabled?`. This commit makes it easier to confirm whether there's suspicious test skip by RubyVM::MJIT.enabled? or not. After this commit, tentatively we're not skipping tests for MJIT other than `assert_no_memory_leak` ones. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65311 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'test/-ext-')
1 files changed, 0 insertions, 4 deletions
diff --git a/test/-ext-/gvl/test_last_thread.rb b/test/-ext-/gvl/test_last_thread.rb
index 7f75c0e..6808e96 100644
@@ -3,10 +3,6 @@ class TestLastThread < Test::Unit::TestCase
# [Bug #11237]
- if defined?(RubyVM::MJIT) && RubyVM::MJIT.enabled?
- skip 'spurious wakeup unavoidable with MJIT'
assert_separately(, <<-"end;") #do