I'd be really curious to see the full output of a Capistrano run that appeared to complete successfully, and yet terminated with a non-zero exit code.
- Jamis On Wed, Jun 17, 2009 at 4:03 AM, Lee Hambley<[email protected]> wrote: > Hey, > Someone (joe?) was hanging out in IRC last night asking about why capistrano > always returned the "failed" exit code when it appeared to complete > sucessfully.... I can think of two potential reasons: > > Your server having written to STDERR caused Capistrano to consider that > that's an error.... > Equally likely.... this Ruby 1.8.7 > bug: http://rubyforge.org/tracker/?func=detail&atid=1698&aid=9300&group_id=426 > > Just what I know, anything anyone else knows would be great! > - Lee > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
