Benoit Daloze

Yes, at least for now. Would still be nice if this is fixed though. The Fiddle issues I found so far with that PR on TruffleRuby looked trivial to fix,...

Is there a way to print the native backend? I'll try to reproduce in GitHub Actions, indeed locally it works for me too on Linux.

I cannot reproduce directly in setup-ruby's CI: https://github.com/ruby/setup-ruby/runs/493299557?check_suite_focus=true

The warning occurs at ``` rubygems/test/rubygems/test_gem_ext_cmake_builder.rb:15: warning: system does not support options in JRuby yet: {:out=>"/dev/null", :err=>[:child, :out]} ``` But that shouldn't even execute in CI: https://github.com/rubygems/rubygems/blob/baebef66cecc68649c386038055e62019479b5c8/test/rubygems/test_gem_ext_cmake_builder.rb#L13-L15 ```ruby skip "CmakeBuilder...

Issue for GitHub Actions to add a CI env var: https://github.com/actions/virtual-environments/issues/520

> since they determined that the lookup scope is static. FWIW it's not always the case, but most of the times it is. ```ruby [Object.new, Object.new].each do |obj| class

@rafaelfranca Thank you for opening this issue, I'm looking at that as well as part of https://github.com/oracle/truffleruby/issues/1837 As a short term workaround we can probably just ignore precompiled gems on...

I found a workaround by setting the `Gem.platforms` in the TruffleRuby-specific RubyGems setup to only `[Gem::Platform::RUBY]`. That seems to work OK, but might break a few RubyGems tests.

https://github.com/oracle/truffleruby/commit/6da9d7c2acf4adcd6bda5c49c2a76027ed02feb6 is the workaround as mentioned above, it seems to work well. It would still be better to consider RUBY_ENGINE in `Gem::Platform` though, as that would allow having gems precompiled...

One step towards improving this: https://github.com/rubygems/rubygems/pull/3817