`--success last` does not work while `--success first` does

Expectation Switching the order of two commands while simultaneously switching from --success last to --success first should not change the exit status of concurrently

Observed behaviour --success last does not work as expected when used together with --kill-others

Version 4.1.0

Steps to reproduce Take two commands: sleep 5; exit 0; and sleep 100, and switch their order. With --success first works correctly:

$> concurrently --kill-others --success first 'sleep 5; exit 0;' 'sleep 100'
[0] sleep 5; exit 0; exited with code 0
--> Sending SIGTERM to other processes..
[1] sleep 100 exited with code SIGTERM
$> echo $?
0

With --success last works incorrectly (expected to get exit code 0 same as above):

$> concurrently --kill-others --success last 'sleep 100' 'sleep 5; exit 0;'
[1] sleep 5; exit 0; exited with code 0
--> Sending SIGTERM to other processes..
[0] sleep 100 exited with code SIGTERM
$> echo $?
1

[paescuj]

Implemented by #318 which has been released in v7.2.0.

[gustavohenke]

Does the above help anyone? 🙂