#16713: Random failure in lseries_ell.py
-------------------------------+-------------------------------
   Reporter:  vbraun           |            Owner:
       Type:  defect           |           Status:  new
   Priority:  major            |        Milestone:  sage-6.3
  Component:  elliptic curves  |         Keywords:  random_fail
  Merged in:                   |          Authors:
  Reviewers:                   |  Report Upstream:  N/A
Work issues:                   |           Branch:
     Commit:                   |     Dependencies:
   Stopgaps:                   |
-------------------------------+-------------------------------
 This is a somewhat regular occurrence on mod:
 {{{
 sage -t --long src/sage/schemes/elliptic_curves/lseries_ell.py
 **********************************************************************
 File "src/sage/schemes/elliptic_curves/lseries_ell.py", line 243, in
 sage.schemes.elliptic_curves.lseries_ell.Lseries_ell.zeros
 Failed example:
     E.lseries().zeros(2)
 Expected:
     [0.000000000, 5.00317001]
 Got:
       ***   Warning: not enough memory, new stack 1000000000.
     [0.000000000, 5.00317001]
 }}}
 There seems to be plenty of free space. Obviously there is enough memory
 to finish the computation and arrive at the correct result, so there
 shouldn't be any warning printed. Related tickets that patched up similar
 issues:
 * Trac #11985: lcalc is too verbose (mysterious "Warning: new stack size")
 * Trac #14470: Relax PARI warnings

--
Ticket URL: <http://trac.sagemath.org/ticket/16713>
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