ruby.git/test/ruby/test_thread_cv.rb, branch v4.0.4 The Ruby Programming Language test_thread_cv.rb: Increase a timeout for a thread test 2025-09-02T17:34:49+00:00 Takashi Kokubun takashikkbn@gmail.com 2025-09-02T17:34:38+00:00 b1b4984fb94fc3d3c17237f8a6a3f8fe90996846 https://github.com/ruby/ruby/actions/runs/17410747983/job/49427074277 
https://github.com/ruby/ruby/actions/runs/17410747983/job/49427074277
Remove stale tests 2023-03-10T02:54:59+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2023-03-10T02:54:59+00:00 0a466e30726a259907bb6f73557faa22d89545ee These tests were added at a198bb3929a4562a12b4aa245a297c7d3695149f, when these classes were `Struct`s. Since these classes have been rewritten, these tests no longer make sense. 
These tests were added at a198bb3929a4562a12b4aa245a297c7d3695149f,
when these classes were `Struct`s.  Since these classes have been
rewritten, these tests no longer make sense.
Reap rarely leaked threads 2021-10-14T13:57:45+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2021-10-14T13:56:42+00:00 c19685e208401594c1a21256382eacfadc22d53a 






Distinguish signal and timeout [Bug #16608]
2021-07-25T20:09:03+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2020-02-06T00:14:40+00:00

070557afc4ca83876b951fe090806b59e3867ae5












Prefer qualified names under Thread
2021-06-29T02:41:10+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-06-28T14:01:53+00:00

9eae8cdefba61e9e51feb30a4b98525593169666












revisit more MJIT test skips
2018-10-22T15:49:22+00:00

k0kubun
k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e

2018-10-22T15:49:22+00:00

e38a0b46067fd261a88be608787927ccdf5b7877

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





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







Move obsoleted test/thread/test_*.rb with the current implementation.
2018-07-31T03:49:38+00:00

hsbt
hsbt@b2dd03c8-39d4-4d8f-98ff-823fe69b080e

2018-07-31T03:49:38+00:00

8bcf27527cbc84622e522ed587a175ada4809360

  * test/ruby/test_thread_{cv,queue}.rb: Move under the test/ruby directory.
    and rename TestThread* from Test*.
  * test/test_sync.rb: Move toplevel of test diretory because sync is still
    standard library.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64137 b2dd03c8-39d4-4d8f-98ff-823fe69b080e





  * test/ruby/test_thread_{cv,queue}.rb: Move under the test/ruby directory.
    and rename TestThread* from Test*.
  * test/test_sync.rb: Move toplevel of test diretory because sync is still
    standard library.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64137 b2dd03c8-39d4-4d8f-98ff-823fe69b080e