-
-
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
Output of backticks call not returned but written to stdout instead #4515
Comments
Wow, this seems super unlikely to be broken since there are definitely backquote tests in various test suites we run. I also can't confirm what you're seeing:
Perhaps something's weird with your shell? I have no explanation for what you're seeing, but if either of those behaviors were actually happening we'd have dozens of broken tests. |
I could reproduce it now on a fresh digitalocean instance with Ubuntu 16.04, without any additional configuration, with java installed from the package
With
|
Please excuse my ignorance regarding Java versions - since Downgrading openjdk works fine for me, so I'm closing this issue, feel free to reopen if openjdk-9 compatibility is desired. |
Actually I do want to look into those. We have not focused on JDK9 support, but we should do that soon. |
We'll do a push for Java 9 in the 9.2 cycle. |
I can confirm that issue exists on JRuby 9.1.14.0 + JDK 9.0.1. |
This appears to work fine on 9.1.16.0 + Java 9.0.1. Please let us know if it's still causing problems. |
Expected Behavior
Output of command is returned from calling backticks, like in this working example on MRI (2.3.3):
Actual Behavior
Output is written to stdout, and the return value of the backticks call is an empty string:
Environment
Ubuntu 16.04 / Linux 4.4.0-042stab120.6
jruby 9.1.7.0 (2.3.1) 2017-01-11 68056ae OpenJDK 64-Bit Server VM 9-internal+0-2016-04-14-195246.buildd.src on 9-internal+0-2016-04-14-195246.buildd.src +jit [linux-x86_64]
I observed this on two machines with Ubuntu 16.04 from different providers, with both jruby 9.1.6.0 and 9.1.7.0. On my local machine with ArchLinux and jruby 9.1.7.0 it behaves as expected.
Same with popen:
Verifying that output goes to stdout:
Is that a bug or could it be some kind of misconfiguration on the Ubuntu servers? Any hints appreciated.
The text was updated successfully, but these errors were encountered: