JRuby on Windows: "bundler: command not found: rake"

[ruby]

JRuby on Windows: "bundler: command not found: rake"

[eregon]

@dentarg That's something else.

I think the issue is JRuby seems to fail to find executables without arguments on Windows ( bundle exec rake default works, but bundle exec rake doesn't).

[eregon]

I reported the bug to JRuby as well, since I think it might be a JRuby bug: jruby/jruby#6053

[slonopotamus]

I reported this bug to Bundler some time ago: rubygems/bundler#7602. It can be reproduced on any Windows machine with JRuby, it isn't specific to GitHub Actions.

[eregon]

I'm unsure what's going on.
Could you try if first installing latest bundler (gem install bundler) helps? Shouldn't be necessary, but at least would rule out a Bundler bug already fixed.

[eregon]

I assume JRuby on Windows should work out-of-the-box, right?

That's the aim but my impression is very few people run JRuby in Windows CI in general.
I know little about Windows, even less so about JRuby on Windows.

For instance, I had to figure out myself which launchers to keep and how to get a ruby alias for jruby (jruby/jruby#6042).

[eregon]

One issue I noticed is ruby -v picks up the system ruby when run with shell: bash:
https://github.com/eregon/setup-ruby-test/runs/433744376
That's not good.

[eregon]

Various issues here, once again with how to provide a ruby alias for jruby that works in both PowerShell and Bash:

• ruby -v in bash just fails on Windows if there is only ruby.bat: https://github.com/eregon/setup-ruby-test/runs/433780474?check_suite_focus=true
• cp jruby.sh ruby fails because JRuby's .sh launcher is broken on Windows in JRuby 9.2.9.0: https://github.com/eregon/setup-ruby-test/runs/433786338?check_suite_focus=true
• cp jruby.exe ruby.exe fails in PwSh: https://github.com/eregon/setup-ruby-test/runs/433787577?check_suite_focus=true

[eregon]

• cp jruby.bash ruby kind of works but incorrectly deals with double quotes ("), which is fairly confusing: https://github.com/eregon/setup-ruby-test/runs/433791906?check_suite_focus=true
  MRI handles the double quotes fine: https://github.com/eregon/setup-ruby-test/runs/433791899?check_suite_focus=true

[eregon]

Here is a final run:
https://github.com/eregon/setup-ruby-test/runs/433804429?check_suite_focus=true

Still bundler: command not found: rake.
This must be a JRuby bug, since it works fine on MRI, and installing rake via bundle install generate very similar rake.bat and rake files for both MRI and JRuby.
Could you report it to https://github.com/jruby/jruby/issues ?

I'll fix the PATH issue, but long story short it doesn't seem the cause here.

[eregon]

OK, this is fun bundle exec rake --version and bundle exec rake default work, but bundle exec rake doesn't!
https://github.com/eregon/setup-ruby-test/runs/433859430

Run bundle exec rake --version
rake, version 13.0.1
Run bundle exec rake default
OK
Run bundle exec rake
bundler: command not found: rake
Install missing gem executables with `bundle install`
##[error]Process completed with exit code 1.

[eregon]

I released 1.41.1 which fixes the PATH so there is no default MRI in PATH, just JRuby.
Now ruby --version and bundle exec rake --version works in both PwSh and Bash.

The rest (bundle exec rake broken) is I believe a JRuby bug, please report it there, I don't think I can do anything about it.

[dentarg]

@eregon thanks for debugging the issue, I saw your comment at jruby/jruby-launcher#29 (comment), is that something else so I should file another jruby issue about this?

[eregon]

@slonopotamus Thanks!
I would guess a JRuby issue since it works fine on MRI, and I would think the code for bundle exec doesn't really rely on the interpreter name. But one never knows.

[slonopotamus]

This was fixed on Bundler side: rubygems/rubygems#3256 (comment)

[eregon]

Seems to be an issue again: jruby/jruby#6053 (comment)

[dentarg]

Seems to be an issue again: jruby/jruby#6053 (comment)
This was fixed on Bundler side: rubygems/rubygems#3256 (comment)

Just an update for anyone finding this thread via search or something, it was concluded that the issue is still with Bundler, rubygems/rubygems#3256 is still open at the time of writing this.

[eregon]

Another update, it is a bug in JRuby, fixed on master but not yet released: jruby/jruby#6745