-
Notifications
You must be signed in to change notification settings - Fork 552
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
Change default exit code behavior to match norm #521
base: main
Are you sure you want to change the base?
Conversation
As you can see it breaks the thor test suite. We need to make sure everything passes. |
Dang, it looks like this is failing due to a 500 response from coveralls.io . All the tests actually pass. I wonder if the run could be retried, or maybe this branch could be rebased, which would retry the run. |
No, it is not failing because of coveralls.io. There is a legit test failing:
|
Oh, sorry, it is just on the 1.8.7 build, I see. |
I'm sorry I made this PR and just abandoned it. I'm going to work on fixing these tests now. |
Alright, we've got a green build. @rafaelfranca can you take another look at this? Also, I just noticed #578. I'm not sure if/how this relates to that change. Maybe @jmax315 can elaborate |
It looks like, on casual inspection, we both fixed the same two problems, although we came at it from two different symptoms. It may still be worth pulling in my specs though (spec/fixtures/exit_status.thor and spec/script_exit_status.rb), as they directly address the symptom that started me off. |
Fixes #244