Conversation
|
Just pinging back on this. Looking at https://github.com/ruby/actions/actions/workflows/snapshot-ruby_3_2.yml, there are still intermittent failures/errors. Not sure about the cause. But, the timing shown in https://bugs.ruby-lang.org/issues/19246#note-7 still applies. Ruby 2.7, 3.0, and head are working as expected. I haven't built a recent ruby_3_1 stable, but testing with |
|
#8252 addressed a blocker for us migrating to Ruby 3.2. Would very interested in an update on the status of this issue. |
|
Applied the patch again at 5baf94f and see no failure in CI at this time. |
4 participants
Reverts #8252
I suspect that #8252 could introduce a
[BUG] object allocation during garbage collection phaseerror.https://github.com/ruby/actions/actions/runs/5942679604/job/16116356743
https://github.com/ruby/actions/actions/runs/5955117204/job/16153242195
https://github.com/ruby/ruby/actions/runs/5932543614/job/16086524440
Let's consider reverting it and observe the results for a while.