BUG: fixed Scripts/antsAtroposN4.sh not stopping when subcommands exit with exitcode>0 #1456
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scripts/antsAtroposN4.sh was not stopping as "${PIPESTATUS[0]}" was always 0, this happened because of "logCmdOutput=" which I this starts a subshell which have the PIPESTATUS variable inside it, but this variable is not visable outside the subshell. The PIPESTATUS is now instead return by the subshell and its exitcode is inserted into cmdExit.
commands use to reproduce the problem:
which should fail because of the missing -x parameter.