Currently, the exit code is not propagated to the scheduler job exit code. I would like a better standard for handling job exit codes. Currently, I trap the exit code with something like this:
$CMD
exit_code=$?
...
exit $exit_code
But if I do this, that means the harness's log_binary_execution.py cannot capture the exit code.
Currently, the exit code is not propagated to the scheduler job exit code. I would like a better standard for handling job exit codes. Currently, I trap the exit code with something like this:
But if I do this, that means the harness's log_binary_execution.py cannot capture the exit code.