Benoit Daloze

> Hmm, I have no idea to do for this issue. It would be a problem of ruby-build or rbenv, or maybe homebrew? To clarify this is an issue of...

I will close this one, sorry, because Ractor seems (currently at least) very much an experimental CRuby-specific feature. The reasoning in more details is in https://github.com/ruby/spec/pull/1043#issuecomment-1930313473

@dushyantss Yes of course, since it's not checked, I'll try to review it soon.

I'm one of the TruffleRuby maintainers, it would be great to get official support for TruffleRuby in Mastodon. I got it to run locally as that tweet mentions. `bundle install`...

FWIW, we'll wait until the 3.1 or 3.2 PR is merged (https://github.com/mastodon/mastodon/pull/22585 and https://github.com/mastodon/mastodon/pull/22928), TruffleRuby master tracks 3.1, and it seems best to wait that fixes for 3.1/3.2 compat are...

The 3.2 PR got merged: https://github.com/mastodon/mastodon/pull/22928 I'm still for benchmark(s) for Mastodon, are there any?

For reference, that's https://github.com/mastodon/mastodon/pull/22585 (and https://github.com/mastodon/mastodon/pull/22928)

> This makes the repeat have annoying warnings about already defined consts. What about just ignoring those warnings for that use case? For example by running specs with `$VERBOSE =...

Redefining constants seems rather harmless in the context of MSpec, when it's not autoload constants. OTOH it's true it's global state that "leaks" between repeated runs of the same specs...

@hsbt Could you review this too? (if not, who should I ask?) (I rebased to make sure it runs the CI with the truffleruby jobs too)