#16938: Sage debug version
-------------------------------------+-------------------------------------
Reporter: SimonKing | Owner:
Type: defect | Status: needs_review
Priority: critical | Milestone: sage-6.4
Component: build | Resolution:
Keywords: debug singular | Merged in:
cygwin64 | Reviewers:
Authors: Simon King, | Work issues:
Volker Braun | Commit:
Report Upstream: Reported | 37fda1dff0d1f58d7b07489a250526d735a12c62
upstream. No feedback yet. | Stopgaps:
Branch: |
u/vbraun/sage_debug_version |
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by vbraun):
They are doctests, not benchmarks. Don't confuse the two. Really, showing
off what size of a problem you can do in doctests is just an overall drag
on development as people have to wait longer and longer for tests. IMHO 12
seconds is already on the long side, you should aim for <=5 for long
tests.
Put differently, would you rather
a) have a buildbot with `SAGE_DEBUG`, or
b) doctest a huge computation and then discard the result because it can't
do anything useful with the timings obtained.
--
Ticket URL: <http://trac.sagemath.org/ticket/16938#comment:42>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
