Code review comment for ~lucaskanashiro/ubuntu/+source/ruby3.1:fix-segfault

Curiously enough, this is almost the same failure that's causing the ruby3.0 FTBFS on Jammy (from your PPA):

  1) Failure:
TestThreadQueue#test_thr_kill [/<<PKGBUILDDIR>>/test/ruby/test_thread_queue.rb:153]:
only 37/250 done in 60 seconds.

  2) Error:
TestThread#test_signal_at_join:
Timeout::Error: execution of assert_separately expired timeout (120 sec)
pid 30807 exit 1
|
| -:27:in `gets': Exception raised: (MiniTest::Assertion)
| <#<SignalException: SIGTERM>>
| Backtrace:
| -:27:in `gets'
| -:27:in `block (3 levels) in <main>'
| -:21:in `times'
| -:21:in `block (2 levels) in <main>'
| /<<PKGBUILDDIR>>/tool/lib/test/unit/core_assertions.rb:185:in `assert_nothing_raised'
| -:20:in `block in <main>'
| -:10:in `popen'
| -:10:in `<main>'.
| from -:27:in `block (3 levels) in <main>'
| from -:21:in `times'
| from -:21:in `block (2 levels) in <main>'
| from /<<PKGBUILDDIR>>/tool/lib/test/unit/core_assertions.rb:185:in `assert_nothing_raised'
| from -:20:in `block in <main>'
| from -:10:in `popen'
| from -:10:in `<main>'
| -:27:in `gets': SIGTERM (SignalException)
| from -:27:in `block (3 levels) in <main>'
| from -:21:in `times'
| from -:21:in `block (2 levels) in <main>'
| from /<<PKGBUILDDIR>>/tool/lib/test/unit/core_assertions.rb:185:in `assert_nothing_raised'
| from -:20:in `block in <main>'
| from -:10:in `popen'
| from -:10:in `<main>'

    /<<PKGBUILDDIR>>/test/ruby/test_thread.rb:1359:in `test_signal_at_join'

Finished tests in 1895.138193s, 9.9265 tests/s, 1403.2386 assertions/s.
18812 tests, 2659331 assertions, 1 failures, 1 errors, 56 skips

From https://launchpadlibrarian.net/720546188/buildlog_ubuntu-jammy-armhf.ruby3.0_3.0.2-7ubuntu2.5~ppa1_BUILDING.txt.gz

I wonder if this is a flaky test.