This assertion failure does not reproduce since https://github.com/ruby/ruby/commit/09aab7899fa0d0014e458c319e689175881a2075 so I think we can close it.yahonda (Yasuo Honda)
On ruby-head, the Active Support (Rails) test suite fails with two Ractor-related errors (rails-nightly build 4651, https://buildkite.com/rails/rails-nightly/builds/4651#01a016ac-eada-492d-9548-44089079b973/L8324). Rails CI failure. T...yahonda (Yasuo Honda)
Correction on the bisect result. 98f0921f2b is where the forked RailtieTest children start to crash (SIGSEGV or ArgumentError), not where this NoMethodError starts. Bisecting for the NoMethodError itself, with the same bin/test command, ...yahonda (Yasuo Honda)
The crash does not reproduce on master, so bisecting from the 4.0 branch point (d375bcc965d4) gives the first fixed commit: > 1da540aeaa1507af4c050bf8a6ee2802e65f9aac "Invalidate CC on cme free as well" (gc.c, +3/-1) The boundary i...yahonda (Yasuo Honda)
Yes. Rails CI builds its test images FROM ruby:3.3 / ruby:3.4 / ruby:4.0, so each lane automatically follows the latest patch release. As far as I remember, this signature had not appeared on any 4.0 release before 4.0.6 — that is a...yahonda (Yasuo Honda)
Recently Rails CI sometimes got SEGV. ## Steps to reproduce Run the Rails (rails/rails main branch) ActiveRecord test suite on Ruby 4.0.6, as Rails CI does. For example: ``` $ git clone https://github.com/rails/rails.git $ cd...yahonda (Yasuo Honda)
This issue was found at Rails Nightly CI https://buildkite.com/rails/rails-nightly/builds/4522#019f393b-4212-453f-8f4f-c1a538af23e5/L3911 ### Steps to reproduce 1. Install these packages (this repro uses Ubuntu 26.04) ``` sudo apt-...yahonda (Yasuo Honda)
This issue is originally found at https://github.com/rails/rails/issues/57954 ### Steps to reproduce 1. Build ruby with `-DRUBY_DEBUG=1` enabled like ``` #!/bin/bash cd ${HOME}/src/github.com/ruby/ruby make clean make dist...yahonda (Yasuo Honda)