Always quit with the correct exit code

[addaleax]

Quit with the exit code of the first failing child, even if the other children exit very fast after the failing child.

Output with the current master:

$ ./index.js -v true false true ; echo $?
`exec true` ended successfully


### Status ###
`exec true` finished
`exec false` is still running
`exec true` is still running


`exec false` failed with exit code 1
`exec true` will now be closed
`exec true` will now be closed


### Status ###
`exec true` finished
`exec false` errored
`exec true` is still running


0

This patch changes the output code to 1. If you have a better solution and/or understanding of the problem, feel free to discard this PR, but the underlying issue is real.

[keithamus]

Hey @addaleax thanks for the PR.

Looking at the code, I think we already do exit if the code > 0, also I think this may break the --wait feature. Sadly this is a difficult problem to solve, but we're on it - check out #30 and more importantly mysticatea/npm-run-all#10

[keithamus]

I think I'll close this. Thanks very much for the PR though. If you feel like helping out, once we close mysticatea/npm-run-all#10 I'll deprecate this repo and we would absolutely love to see you over in http://github.com/mysticatea/npm-run-all raising issues and making PRs 😄

[addaleax]

Okay, thanks for the info!