Misc #22001: Adding TruffleRuby in the CI of all default & bundled gems

• Status: Open
• Assignee: -

[Eregon (Benoit Daloze)]

I would like to add TruffleRuby (i.e. ruby-version: truffleruby, the latest release for improved stability) in the CI of all default & bundled gems.
I'm tracking the progress in https://github.com/truffleruby/truffleruby/issues/2644.

The reason is default & bundled gems are more likely to depend on CRuby internals or CRuby specifics, and have a very large blast readius, and so adding TruffleRuby there would help to avoid such gems breaking unknowingly on TruffleRuby, which has happened a number of times in the past (and similarly on JRuby).

The concrete issue is that for some gems without active maintainers (such as in #21922 and more) it can take a (sometimes very) long time to merge the PR adding TruffleRuby in CI.
How can we solve this?

I also don't want TruffleRuby being in CI to be any kind of burden, so if there is any issue with it more frequent than other Ruby versions in CI, it seems fair to remove it or use continue-on-error: true or just ignore the failure.
If removing, my only request would be if possible to include @eregon in the PR description removing the job so I can take a look.
To help keeping CIs green I use truffleruby-gem-tracker and I try to check it regularly to fix any failure.

[Eregon (Benoit Daloze)]

• Related to Misc #21922: Permissions for committers for ex-default/bundled/unbundled gems repositories added