#14365: One doctest in cmdline.py is too touchy with respect to the shebang
--------------------------------+-------------------------------------------
       Reporter:  Snark         |         Owner:  mvngu         
           Type:  enhancement   |        Status:  needs_review  
       Priority:  trivial       |     Milestone:  sage-5.9      
      Component:  doctest       |    Resolution:                
       Keywords:  packaging     |   Work issues:                
Report Upstream:  N/A           |     Reviewers:  Leif Leonhardy
        Authors:  Julien Puydt  |     Merged in:                
   Dependencies:                |      Stopgaps:                
--------------------------------+-------------------------------------------

Comment (by fbissey):

 Just for fun that's what fails in sage-on-gentoo after we patch most of
 what we care of
 {{{
 sage -t -long "devel/sage-main/sage/tests/cmdline.py"
 **********************************************************************
 File "/usr/share/sage/devel/sage-main/sage/tests/cmdline.py", line 196:
     sage: ret
 Expected:
     0
 Got:
     1
 **********************************************************************
 File "/usr/share/sage/devel/sage-main/sage/tests/cmdline.py", line 217:
     sage: print out
 Expected:
     Found package sqlalchemy in spkg/standard/sqlalchemy-...spkg
     = SQLAlchemy =
     ...
     SQLAlchemy is the Python SQL toolkit...
 Got:
     sage-run received unknown option: --info
     usage: sage [options]
     Try 'sage -h' for more information.
     <BLANKLINE>
 **********************************************************************
 File "/usr/share/sage/devel/sage-main/sage/tests/cmdline.py", line 224:
     sage: ret
 Expected:
     0
 Got:
     1
 **********************************************************************
 File "/usr/share/sage/devel/sage-main/sage/tests/cmdline.py", line 347:
     sage: print err
 Expected:
     Traceback (most recent call last):
     ...
     RuntimeError: refusing to run doctests...
 Got:
     <BLANKLINE>
 **********************************************************************
 File "/usr/share/sage/devel/sage-main/sage/tests/cmdline.py", line 352:
     sage: print err
 Expected:
     Traceback (most recent call last):
     ...
     RuntimeError: refusing to run doctests...
 Got:
     Traceback (most recent call last):
       File "/usr//bin/sage-ptest", line 446, in <module>
         p = multiprocessing.Pool(numthreads)
       File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 232,
 in Pool
         return Pool(processes, initializer, initargs, maxtasksperchild)
       File "/usr/lib64/python2.7/multiprocessing/pool.py", line 129, in
 __init__
         raise ValueError("Number of processes must be at least 1")
     ValueError: Number of processes must be at least 1
     <BLANKLINE>
 **********************************************************************
 }}}
 I'd like to dig the problem with the value from "ret" in 2 tests. The
 sqlalchemy tests really duplicate testing in another part of sage I am
 sure. My solution for that will be to eventually remove it surgically
 since the only sage spkg handling functionality that it is working and
 intend to keep is to produce spkg.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14365#comment:10>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to