Bug #21613
open
TestGc#test_exception_in_finalizer_procs and TestGc#test_exception_in_finalizer_method fail with ASAN
Description
See https://github.com/ruby/ruby-dev-builder/actions/runs/17883721287/job/50854696068
1) Failure:
TestGc#test_exception_in_finalizer_procs [/home/runner/work/ruby-dev-builder/ruby-dev-builder/test/ruby/test_gc.rb:828]:
pid 40237 exit 0.
1. [1/2] Assertion for "stdout"
| <["c1", "c2"]> expected but was
| <["c1"]>.
2) Failure:
TestGc#test_exception_in_finalizer_method [/home/runner/work/ruby-dev-builder/ruby-dev-builder/test/ruby/test_gc.rb:848]:
pid 40260 exit 0.
1. [1/2] Assertion for "stdout"
| <["c1", "c2"]> expected but was
| <["c1"]>.
Finished tests in 630.155129s, 46.2553 tests/s, 9737.2404 assertions/s.
29148 tests, 6135972 assertions, 2 failures, 0 errors, 178 skips
Oddly enough https://ci.rvm.jp/results/trunk_asan@ruby-sp1 doesn't fail.
This is not the first time, it's been many times that job found issues not caught in ruby/ruby CI, so I would like to request adding a ASAN GHA job doing the same as https://github.com/ruby/ruby-dev-builder in ruby/ruby so such failures are found earlier and do not block ruby-dev-builder and setup-ruby.
If not, I will be forced to drop ASAN support in setup-ruby.
For now I will exclude these tests on ASAN to unblock, but it's a bit hacky because there seems to be no predicate to detect ASAN, except Thread.asan? with require '-test-/stack' (= hacky).
Also see https://ruby.slack.com/archives/C02A3SL0S/p1758466605889269
Updated by Eregon (Benoit Daloze) 1 day ago
Excluded in 02299d68bcb0e6eabab2b973b28e9dafbafe6149