diff options
| 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 |
| commit | e38a0b46067fd261a88be608787927ccdf5b7877 (patch) | |
| tree | 216dd07d4c2e0b5453d4cc195e52f0914d166334 /test/ruby/test_thread_cv.rb | |
| parent | 7f5bb3082d9190f24a9839182aafd1ae670b4b13 (diff) | |
| download | ruby-e38a0b46067fd261a88be608787927ccdf5b7877.tar.gz | |
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/ruby/test_thread_cv.rb')
| -rw-r--r-- | test/ruby/test_thread_cv.rb | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/test/ruby/test_thread_cv.rb b/test/ruby/test_thread_cv.rb index 4161ba2341..38bcc3b8fa 100644 --- a/test/ruby/test_thread_cv.rb +++ b/test/ruby/test_thread_cv.rb @@ -33,8 +33,6 @@ class TestThreadConditionVariable < Test::Unit::TestCase end def test_condvar_wait_exception_handling - skip "MJIT thread is unexpected for this test, especially with --jit-wait" if RubyVM::MJIT.enabled? - # Calling wait in the only thread running should raise a ThreadError of # 'stopping only thread' mutex = Mutex.new |