#7995: sage-test doesn't handle all of sage-doctest's return values
-----------------------+----------------------------------------------------
Reporter: wjp | Owner: tbd
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.3.2
Component: doctest | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Changes (by nthiery):
* status: needs_review => needs_work
Comment:
I don't know much the doctest framework. But the code looks good, and this
removes two seriously annoying misfeatures of doctests. Thanks so much for
scratching this itch for me!
Quick remarks:
- When there is an exception in the doctesting framework; will we get
a traceback? That would be most handy!
- in "... Check the process exit codes ...": codes -> code?
- The following two comments seem contradictory. Or am I
misunderstanding something?
> # Return value in process exit code:
> # 0: all tests passed
> # 1: file not found
> # 2: KeyboardInterrupt
> # 3: doctest process was terminated by a signal
> # 4: the doctesting framework raised an exception
> # 100: failed doctests
> ####################################################################
>
> def test_code(filename):
> # Return value in the doctest process exit code:
> # 0: everything passed
> # 1-253: number of failed doctests
> # 254: >= 254 doctests failed
> # 255: exception raised by doctesting framework
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7995#comment:3>
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.