Failure to connect to Nailgun server produces confusing error
-------------------------------------------------------------
Key: JRUBY-5973
URL: https://jira.codehaus.org/browse/JRUBY-5973
Project: JRuby
Issue Type: Bug
Components: Launcher
Affects Versions: JRuby 1.6.3
Reporter: Charles Oliver Nutter
Assignee: Charles Oliver Nutter
Fix For: JRuby 1.6.4
When the NG server is not up, jruby --ng produces only the following error:
{noformat}
~/projects/jruby $ jruby --ng -e 1
connect: Connection refused
{noformat}
This error gives no indication as to the actual cause of the problem. If
instead it reported "connect to Nailgun server: Connection refused" there would
be less chance of confusing this error for a Ruby error.
This actually confused the Travis CI folks into thinking there was a network
connectivity problem or JRuby bug affecting RubyGems or Bundler, when in
actuality the problem was caused by RVM using Nailgun and (probably) not having
the server initialized before the command launched. A better error message
would have shown the problem very quickly.
We should fix this in the launcher, and possibly in our copy of ng client
source. If we do the latter, we should also attempt to submit a patch back to
the ng authors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
