#12272: More # long time additions
----------------------------------+-----------------------------------------
Reporter: jdemeyer | Owner: mvngu
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-5.0
Component: doctest | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by jdemeyer):
Replying to [comment:12 cremona]:
> I got here too late to help, it seems. I think we might want a
discussion on sage-devel about the role of long tests. Whenever I test a
beta build I run all the long tests anyway (what's the point otherwise?),
and casual users will not run any tests.
`# long time` serves purposes beyond that:
1. non-long tests are actually used, for example the patchbot does non-
long tests only.
2. "long time" serves as documentation to the user that some command is
supposed to take a long time.
3. keeping track of the runtime of these tests makes it possible to
detect regressions. For example, for the `integral_points()` tests, it
was marked as taking 35s but I found it actually took 50s. I agree "long
time" isn't the best solution for this, but it's the best we currently
have.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12272#comment:13>
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.
