#9449: The summary printed after running doctests is inaccurate.
------------------------+---------------------------------------------------
Reporter: drkirkby | Owner: mvngu
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.5
Component: doctest | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Comment(by wjp):
The "# failures" that sage reports is calculated very simply by counting
the number of instances of "Expected:" "Expected nothing" and "Exception
raised:".
Sage correctly detected that things went wrong, as you can tell from the
fact that the files causing errors are listed in the summary at the end.
As far as I can tell, the only thing that's not quite right is the
reporting of what exactly went wrong. There's likely a better way of
reporting these specific crashes and missing file errors you're getting,
but I don't see any reason to believe something is as seriously wrong with
the error reporting as you seem to be implying on this ticket and on the
mailing list.
(Reverting priority to major.)
The file not found errors (Are you out of disk space?) should probably be
caught before the doctesting process is launched in the first place. I'll
have to think about the SIGBUS case some more.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9449#comment:11>
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.
