[GitHub] [incubator-mxnet] mozga-intel edited a comment on pull request #20683: [master][bugfix] Remove exit 0 to avoid blocking in CI pipeline

[GitBox <gi...@apache.org>]

mozga-intel edited a comment on pull request #20683:
URL: https://github.com/apache/incubator-mxnet/pull/20683#issuecomment-947785088


   > I'm not sure I can follow you.
   > 
   > Exit 0 means continue, non-zero means abort. To me it seems like you're rather disabling CI rather than fixing the issue clang is revealing and thus aborting... Or is this called in a chain of commands?
   
   @marcoabreu 
   From man bash on return [n] 
   
   > Exit 0 means continue, non-zero means abort. To me it seems like you're rather disabling CI rather than fixing the issue clang is revealing and thus aborting... Or is this called in a chain of commands?
   
   on exit [n] 
   
   > Cause the shell to exit with a status of n. If n is omitted, the exit status is that of the last command executed. A trap on EXIT is executed before the shell terminates.
   
   Finally, functions, when called, the exit 0 (within the function) exits a code ~ without a failure. The return has nothing to do with exit codes.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@mxnet.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org