Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: JRuby 1.7.0.RC1
-
Fix Version/s: JRuby 1.7.0.RC2
-
Component/s: Ruby 1.9.3
-
Labels:None
-
Environment:Windows 7 / Windows Server 2008 R2
JRuby 1.7.0.RC1
Bundler 1.2.1
-
Number of attachments :
Description
With JRuby 1.7.0.preview1 the following works fine:
bundle exec "rake routes"
With JRuby 1.7.0.RC1 the above command is broken, as are:
bundle exec "rake assets:clean"
bundle exec "rake assets:precompile"
etc.
When any of the above are run, the following exception is thrown:
Unfortunately, a fatal error has occurred. Please see the Bundler
troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
SystemCallError: Unknown error - No message available
_exec_internal at org/jruby/RubyKernel.java:1658
exec at file:/C:/jruby/jruby-1.7.0.RC1/lib/jruby.jar!/jruby/kernel19/kernel.rb:23
exec at C:/jruby/jruby-1.7.0.RC1/lib/ruby/gems/shared/gems/bundler-1.2.1/lib/bundler/cli.rb:428
__send__ at org/jruby/RubyBasicObject.java:1673
send at org/jruby/RubyKernel.java:2079
run at C:/jruby/jruby-1.7.0.RC1/lib/ruby/gems/shared/gems/bundler-1.2.1/lib/bundler/vendor/thor/task.rb:27
invoke_task at C:/jruby/jruby-1.7.0.RC1/lib/ruby/gems/shared/gems/bundler-1.2.1/lib/bundler/vendor/thor/invocation.rb:120
dispatch at C:/jruby/jruby-1.7.0.RC1/lib/ruby/gems/shared/gems/bundler-1.2.1/lib/bundler/vendor/thor.rb:275
start at C:/jruby/jruby-1.7.0.RC1/lib/ruby/gems/shared/gems/bundler-1.2.1/lib/bundler/vendor/thor/base.rb:408
(root) at C:/jruby/jruby-1.7.0.RC1/lib/ruby/gems/shared/gems/bundler-1.2.1/bin/bundle:14
with_friendly_errors at C:/jruby/jruby-1.7.0.RC1/lib/ruby/gems/shared/gems/bundler-1.2.1/lib/bundler/friendly_errors.rb:4
(root) at C:/jruby/jruby-1.7.0.RC1/lib/ruby/gems/shared/gems/bundler-1.2.1/bin/bundle:14
load at org/jruby/RubyKernel.java:1045
(root) at C:\jruby\jruby-1.7.0.RC1\bin\bundle:23
I have reproduced this issue. Hopefully, will get to the bottom of it soon. If you want a workaround in the meantime you can probably disable native execution and fall back to pure-Java support via 'set JRUBY_OPTS=-Xnative.enabled=false'. This may or may not be a good enough workaround as pure-Java mode does not emulate every possible thing we use native support for.