summaryrefslogtreecommitdiff
path: root/benchmark/bm_vm4_pipe.rb
diff options
context:
space:
mode:
authorTakashi Kokubun <takashikkbn@gmail.com>2024-04-26 11:11:04 -0700
committerTakashi Kokubun <takashikkbn@gmail.com>2024-04-26 11:11:30 -0700
commita1db69f0c9a8c3cb9e03b1701a82c2ea2c167500 (patch)
tree3d08dfb66c7013a98590bff8f037dec2146f5cd5 /benchmark/bm_vm4_pipe.rb
parent6a296089c61223ca040e6dc3b92d9bbd1c62c309 (diff)
Skip a flaky Ractor test for YJITHEADmaster
https://github.com/ruby/ruby/actions/runs/8852277192/job/24310631888 https://github.com/ruby/ruby/actions/runs/8851325573/job/24307638329 This seems like an existing, separate issue from what we're currently investigating. The `iseq->body->jit_entry` setup is not Ractor-safe? Let me suppress this for now and revisit this after resolving the ongoing issue.
Diffstat (limited to 'benchmark/bm_vm4_pipe.rb')
0 files changed, 0 insertions, 0 deletions