#4610: [with patch, positive review] "sage -tp X": Move certain long doctests to
the start of the list of files to test
------------------------------------+--------------------------
       Reporter:  mabshoff          |        Owner:  gfurnish
           Type:  defect            |       Status:  closed
       Priority:  critical          |    Milestone:  sage-3.2.2
      Component:  doctest coverage  |   Resolution:  fixed
       Keywords:                    |    Merged in:
        Authors:                    |    Reviewers:
Report Upstream:  N/A               |  Work issues:
         Branch:                    |       Commit:
   Dependencies:                    |     Stopgaps:
------------------------------------+--------------------------
Changes (by chapoton):

 * upstream:   => N/A


Old description:

> There are various doctests in Sage that take a while, chief among those
> is
> {{{
> sage -t -long devel/sage/sage/crypto/mq/sr.py
>          [630.4 s]
> }}}
> When running -tp with a high number of parallel threads those tests end
> up running at the end and making the user wait a while until that test
> finishes:
> {{{
> Total time for all tests: 1287.6 seconds
> }}}
> Moving this and a couple other files to the beginning of the list to
> doctest in local/bin/sage-ptest would likely result in a more even
> utilization of the cores. This also annoys me personally since I run -tp
> 8 -long after each patch merged in sage.math and it would shave probably
> 4 minutes off the total time of each run.
>
> Cheers,
>
> Michael

New description:

 There are various doctests in Sage that take a while, chief among those is
 {{{
 sage -t -long devel/sage/sage/crypto/mq/sr.py
  [630.4 s]
 }}}
 When running -tp with a high number of parallel threads those tests end up
 running at the end and making the user wait a while until that test
 finishes:
 {{{
 Total time for all tests: 1287.6 seconds
 }}}
 Moving this and a couple other files to the beginning of the list to
 doctest in local/bin/sage-ptest would likely result in a more even
 utilization of the cores. This also annoys me personally since I run -tp 8
 -long after each patch merged in sage.math and it would shave probably 4
 minutes off the total time of each run.

 Cheers,

 Michael

--

--
Ticket URL: <http://trac.sagemath.org/ticket/4610#comment:6>
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.

Reply via email to