Applied in changeset commit:git|9e0261a9dc1efd17a4698b1a804eb3641520d9da. ---------- [Bug #22057] test-bundler: add `--enable-gems` explicitly This is because `make test-bundler-parallel` command, which runs successfully via turbo_test...tikkss (Tsutomu Katsube)
This is because `make test-bundler-parallel` command, which runs successfully via turbo_tests, does not have `--disable-gems` option specified. `--disable-gems` is currently set in `RUN_OPTS`. Removing it would affect not only test-bund...tikkss (Tsutomu Katsube)
byroot (Jean Boussier) wrote in #note-6: > I understand the reasoning, however given the implementation of boxes, I fear implementing this proposal would reintroduce the need for many ractor locks, negating their usefulness. > ... Than...tikkss (Tsutomu Katsube)
@Eregon Thank you for even creating a verification script. If you are comparing the RSS of only a single process, I think your example is fine. However, I wanted to compare the total RSS including all worker processes. This is becau...tikkss (Tsutomu Katsube)
I have tried to fix this issue at RubyKaigi 2026 on Code Party. However, I was unable to fix it. I have confirmed that this issue has been resolved in 12bb895526. Thanks for your patch!tikkss (Tsutomu Katsube)
test-bundler failed just one example (./spec/bundler/bundler/cli_common_spec.rb:7). However, test-bundler-parallel is successful. I think this is happening because while test-bundler includes the `--disable-gems` option, it is not sp...tikkss (Tsutomu Katsube)
Eregon (Benoit Daloze) wrote in #note-2: > Did you measure the difference in memory usage? > ... Thanks for your reply. No, I didn't. But I took this opportunity to give it a try. I increased the number of classes with three methods to ...tikkss (Tsutomu Katsube)
I describe the use case of test-unit. Now, we are implementing `Ractor` based parallel test runner. The tests are run on non-main ractors. We have met a lot of `Ractor::IsolationError`. Each time, We have tried using `freeze` or ...tikkss (Tsutomu Katsube)
Description --- When Ruby Box is enabled (`RUBY_BOX=1`), `$!` inside `rescue` does not change after the first exception. `$!` is expected to show the exception for each `rescue` block, but it always shows the first one. Steps t...tikkss (Tsutomu Katsube)