{"issue":{"state":"closed","pull_request":{"diff_url":"https://github.com/guard/guard-rspec/pull/66.diff","html_url":"https://github.com/guard/guard-rspec/pull/66","patch_url":"https://github.com/guard/guard-rspec/pull/66.patch"},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/2d643c10e432e230c9d4bf97d15d6a46?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"2d643c10e432e230c9d4bf97d15d6a46","url":"https://api.github.com/users/cgriego","login":"cgriego","id":4805},"assignee":null,"updated_at":"2011-11-14T08:47:14Z","labels":[],"closed_at":"2011-11-11T07:08:20Z","comments":5,"url":"https://api.github.com/repos/guard/guard-rspec/issues/66","body":"Fixes #65\r\n\r\nWhen executing `rspec --failure-exit-code 2` that tells RSpec to return 2 when the specs fail to pass, which is the case handled by the RSpec formatter. When RSpec succeeds, obviously the exit code is 0 and that is also a case handled by the formatter -- but one the error handling code wasn't accounting for. When RSpec fails to run because of an exception while loading the code, then Ruby returns an exit code of 1.\r\n\r\nThe error handling code needs to notify if the error code !=0 and != failure_exit_code.","html_url":"https://github.com/guard/guard-rspec/issues/66","title":"Don't notify of a failure when specs pass","number":66,"id":2191633,"created_at":"2011-11-09T21:39:24Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/d93f02de03e13b5ae9b1bea0d456cc67?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d93f02de03e13b5ae9b1bea0d456cc67","url":"https://api.github.com/users/thibaudgg","login":"thibaudgg","id":1322},"updated_at":"2011-11-14T08:47:14Z","url":"https://api.github.com/repos/guard/guard-rspec/issues/comments/2727848","body":"Ok fixed with `--drb` flag in 0.5.4","id":2727848,"created_at":"2011-11-14T08:47:14Z"}}