#18904: Automatically test optional non-packages (CPLEX, Gurobi, Maple?, ..)
-------------------------+-------------------------------------------------
       Reporter:         |        Owner:
  ncohen                 |       Status:  needs_review
           Type:         |    Milestone:  sage-6.8
  enhancement            |   Resolution:
       Priority:  major  |    Merged in:
      Component:         |    Reviewers:
  doctest framework      |  Work issues:
       Keywords:         |       Commit:
        Authors:         |  698ebe958d528ac279601e0acbbf0c16f00350de
  Nathann Cohen          |     Stopgaps:
Report Upstream:  N/A    |
         Branch:         |
  public/18904           |
   Dependencies:         |
-------------------------+-------------------------------------------------

Comment (by ncohen):

 > > Almost nothing, give it a try.
 {{{
 sage: %time _=DC._default_optional_tags()
 CPU times: user 8 ms, sys: 28 ms, total: 36 ms
 Wall time: 350 ms
 }}}

 That's how long you lose. Compare it with the time it takes to doctest
 control.py (which is not a 'hard' file by any standard)

 {{{
 (tmp|…)~/sage/doctest$ time sage -tp control.py
 ...
 sage -tp control.py  2.94s user 0.45s system 74% cpu 4.530 total
 }}}

 And of course this become totally negligible if you test several files, a
 folder, or the whole of Sage.

 > I don't have those non-open-source packages installed. Ideally it should
 be tested by people ''having the packages installed''.

 If you are talking about CPLEX and Gurobi, then the time it takes to test
 whether they are present is *REALLY* negligible compared to the time it
 takes to test for `maple/mathematica/others`. It is more or less
 equivalent to load a module and interpret the 'nameerror' if the (cython)
 module does not exist. This is done twice, so the cost is very very small.

 For the interface.* guys, I personally don't have them on my computer but
 I consider the time it takes to run the tests to be non-important. If you
 want to use this argument to claim on sage-devel that they should not be
 tested, however, you are of course allowed to.

 Overall, I think that maple/matlab and others should be included in our
 tests, for otherwise they will break forever. Paying `0.5s` in a
 `ptestlong` does not stop me. On the other hand I know that it is useless
 to argue with you when you do not want to hear something, so I am quite
 ready to sacrifice it if you but ask. Just decide something and explain
 the outcode to people on sage-devel who would want this to be tested. I
 did my part.

 Nathann

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