Its tricky to test for memory leaks... if you want to go ahead and remove 
these tests (or add # not tested) then that would be fine with me. Really 
doctests are only useful if they are reproducible.


On Wednesday, January 7, 2015 12:01:56 AM UTC+1, John H Palmieri wrote:
>
> If you mean the failure in singular/polynomial.pyx, it looks more like a 
> memory leak:
>
> sage -t --long src/sage/libs/singular/polynomial.pyx
> **********************************************************************
> File "src/sage/libs/singular/polynomial.pyx", line 166, in 
> sage.libs.singular.polynomial.singular_polynomial_call
> Failed example:
>     leak(10000)
> Expected:
>     0
> Got:
>     83886080
> **********************************************************************
> 1 item had failures:
>    1 of  12 in sage.libs.singular.polynomial.singular_polynomial_call
>
> If I replace the lines
>
>         sage: leak(10000)
>         0
>
> with 10 such doctests and run "sage -t" repeatedly on the file, I get 
> between 1 and 4 failures each time.
>
>
>
> On Tuesday, January 6, 2015 2:45:17 PM UTC-8, Volker Braun wrote:
>>
>> Is the first failure also in the maxima tty interface or elsewhere?
>>
>> I'we seen some OSX pty handling bugs in 
>> http://trac.sagemath.org/ticket/16474, so I'm not really surprised that 
>> there are random failures on Apple machines.
>>
>>
>>
>> On Tuesday, January 6, 2015 5:20:05 PM UTC+1, John H Palmieri wrote:
>>>
>>>
>>> I don't know if you need the whole thing, but here is the end of the 
>>> snippet from ptestlong.log:
>>>
>>> sage: maxima.facts() ## line 664 ##
>>> []
>>> sage: var('a') ## line 666 ##
>>> a
>>> sage: maxima('limit(x^a,x,0)') ## line 668 ##
>>> sage: sig_on_count() ## line 675 ##
>>> 0
>>> sage: maxima._eval_line('1+1;') ## line 729 ##
>>> '2'
>>> sage: maxima._eval_line('sage0: x == x;') ## line 731 ##
>>>
>>> **********************************************************************
>>>
>>>
>>>
>>> On Tuesday, January 6, 2015 12:18:54 AM UTC-8, Volker Braun wrote:
>>>>
>>>> This is a timeout, right? Can you run the test with --verbose and see 
>>>> where it hangs?
>>>>
>>>>
>>>> On Tuesday, January 6, 2015 2:50:40 AM UTC+1, John H Palmieri wrote:
>>>>>
>>>>> On Monday, January 5, 2015 2:38:41 PM UTC-8, Volker Braun wrote:
>>>>>>
>>>>>> As usual, get the "develop" branch or download the self-contained 
>>>>>> source tarball from http://www.sagemath.org/download-latest.html
>>>>>>
>>>>>> On two OS X machines, two of the same failures as in 6.4.beta3:
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> sage -t --long --warn-long 38.0 src/sage/libs/singular/polynomial.pyx  
>>>>> # 1 doctest failed
>>>>> sage -t --long --warn-long 38.0 src/sage/interfaces/maxima.py  # Timed 
>>>>> out
>>>>> ----------------------------------------------------------------------
>>>>>
>>>>> -- 
>>>>> John
>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Reply via email to