RFC Using exit codes to control aborting, blocking workflows

google-code-export / yabi

Automatically exported from code.google.com/p/yabi

0 stars 1 forks source link

RFC Using exit codes to control aborting, blocking workflows #246

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

In our case we have jobs, that if they fail render the whole workflow useless.

Could you add an ability to abort the workflow, so we don't waste valuable HPC 
resources trying to compute something that is not meaningful.

Original issue reported on code.google.com by KVN1...@gmail.com on 6 Jul 2012 at 8:36

GoogleCodeExporter commented 9 years ago

User initiated stopping/aborting workflows is 
https://code.google.com/p/yabi/issues/detail?id=125

Original comment by aahun...@gmail.com on 7 Jul 2012 at 3:09

GoogleCodeExporter commented 9 years ago

Changed the title, to distinguish between user initiated aborting of workflows 
(already ticketed) and an improved method of blocking/aborting automatically 
based on return code.

Original comment by aahun...@gmail.com on 7 Jul 2012 at 3:18

Changed title: RFC Using exit codes to control aborting, blocking workflows
Added labels: Type-Enhancement, Priority-High

GoogleCodeExporter commented 9 years ago

http://tldp.org/LDP/abs/html/exitcodes.html

..and to quote:

There has been an attempt to systematize exit status numbers (see 
/usr/include/sysexits.h), but this is intended for C and C++ programmers. A 
similar standard for scripting might be appropriate. The author of this 
document proposes restricting user-defined exit codes to the range 64 - 113 (in 
addition to 0, for success), to conform with the C/C++ standard. This would 
allot 50 valid codes, and make troubleshooting scripts more straightforward.

Original comment by aahun...@gmail.com on 7 Jul 2012 at 3:21