jruby and bundler-cache: true not playing nicely together

[JacobEvelyn]

It's possible I'm doing something wrong, but I just tried using the bundler-cache: true option and found that it works fine for MRI rubies but for jruby it runs bundle install fine, but then when we run bundle exec rspec we get:

bundler: failed to load command: rspec

(rspec is in the Gemfile.) What am I missing?

[eregon]

Do you have an example workflow run where it fails?

[JacobEvelyn]

Yes, sorry for not linking earlier. Here's the workflow change I'm attempting to make, and here's the result.

[eregon]

Can you try to reproduce locally on JRuby? This sounds like a JRuby bug.

And in previous runs such as https://github.com/panorama-ed/memo_wise/runs/928059400?check_suite_focus=true RuboCop was skipped on JRuby.

[eregon]

But on https://github.com/panorama-ed/memo_wise/runs/925094050?check_suite_focus=true it worked, interesting.
But the cache key in that run doesn't seem very good, it's not per Ruby version:

       key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}

Could you try to run that again (so based on memo_wise master) but without the cache step?

[JacobEvelyn]

Could you try to run that again (so based on memo_wise master) but without the cache step?

Sure! I just pushed a new commit to that testing branch, and it ran successfully, making me think the issue is somewhere in ruby/setup-ruby. Let me know what else I can do to help debug this!

[eregon]

It's a bug of JRuby, I could reproduce it locally: jruby/jruby#6349

[JacobEvelyn]

Thank you!

[headius]

This is not a bug of JRuby. It is a bug of Bundler.

jruby/jruby#6349 (comment)