-
-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SystemCallError: Unknown error - <STDOUT> #4505
Comments
Seem to be able to reproduce this on Java 1.8.0_31 as well. |
Can you reproduce with a build from master? I've never seen this before. If you can get it to happen with more verbosity (turn on backtraces or verbose or whatever in Bundler, maybe pass put I've added some additional info to the error message so we can at least see what type of system error it was trying to raise. |
Good! I'll see if I can reproduce this with a build from master as well. Can it easily be installed on Travis/i.e. using rvm somehow? |
Specifying jruby-head should pull from our more recent green build. I'll make sure we have a green build (things are a little fluxy today). |
I think there should be a good recent build for you to try if you go with jruby-head. We have logic to ping Travis for every green build so they update their pre-built "jruby-head". |
Oh, and if you just want to do it yourself, I believe rvm install jruby-head will just build master fine. |
The problem with my use case is we use a jruby-complete here to run the bundle install. So even though I can |
The snapshot builds at http://ci.jruby.org/ appear to be up to date. |
Thanks @headius. So weird - when trying this snapshot, I cannot reproduce this error any more... I suggest we close it for now; if we find a way to reproduce this with the latest code on |
Environment
Provide at least:
9.1.7.0
Expected Behavior
bundle install
should succed.Actual Behavior
I will try upgrading the Java version to see if it makes any difference.
The text was updated successfully, but these errors were encountered: