#10200: Catch Sphinx WARNING or ERROR
-------------------------------+--------------------------------------------
Reporter: jdemeyer | Owner: GeorgSWeber
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.6.1
Component: build | Keywords: sphinx build documentation
Author: Jeroen Demeyer | Upstream: N/A
Reviewer: Minh Van Nguyen | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Changes (by jdemeyer):
* status: needs_review => needs_work
Comment:
Replying to [comment:9 mvngu]:
> Better still, for my benefit could you please point me to relevant
documentation explaining exit code for the particular situations under
consideration?
I'm afraid there are not much standards about exit codes. The main thing
is that 0 means success and anything else means failure. Also, many
operation systems (if not all) use 1 byte for the exit code, so the range
is ![0,255].
bash uses 128+{{{sig}}} as exit code when a process fails with signal
{{{sig}}}. For example, type {{{cat}}} (without arguments) and press
CTRL-C. Then the exit code will be 130 (= 128 + 2 with {{{SIGINT}}} ==
2):
{{{
$ cat
^C
$ echo $?
130
}}}
Because of this, exit codes are usually in the range ![0,127]. Some
programs use higher numbers to indicate more serious errors (say: 1 for
normal errors, 2 for serious errors), but this is not a general rule.
I will provide a patch with better documented exit codes.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10200#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
