Uh oh!
There was an error while loading. Please reload this page.
test: use Test::Unit::TestCase.ractor - #38
Conversation
Instead of using assert_separately. If we use .ractor, we can use the same process for tests that use Ractor. It's easy to debug.
hsbt
commented
May 1, 2024
Can we use this feature on I'm happy to port this feature to https://github.com/ruby/ruby/blob/master/tool/lib/test/unit/testcase.rb |
kou
commented
May 1, 2024
No.
Right.
Thanks. |
nobu
commented
May 5, 2024
|
https://github.com/ruby/pathname/actions/runs/8895915304/job/24427357987?pr=38#step:5:20
|
kou
commented
May 5, 2024
I think that we don't need to suppress the Ractor warning. So test-unit doesn't suppress the warning automatically. |
nobu
commented
May 5, 2024
Well, it would be a preference matter, like as test-unit shows Also it's because |
kou
commented
May 5, 2024
I see. |
Instead of using assert_separately. If we use .ractor, we can use the same process for tests that use Ractor. It's easy to debug.