#10195: Occasional doctest failure in libs/fplll/fplll.pyx
-----------------------+----------------------------------------------------
   Reporter:  mpatel   |       Owner:  mvngu     
       Type:  defect   |      Status:  new       
   Priority:  major    |   Milestone:  sage-4.6.1
  Component:  doctest  |    Keywords:            
     Author:           |    Upstream:  N/A       
   Reviewer:           |      Merged:            
Work_issues:           |  
-----------------------+----------------------------------------------------

Old description:

> Reported on [http://groups.google.com/group/sage-
> devel/browse_thread/thread/145fb7e073d4e12b sage-devel]:
> {{{
> I ran
>
> ./sage -t -long -force_lib "devel/sage/sage/libs/fplll/fplll.pyx"
>
> 1000 times in serial [1] with a 64-bit 4.6.rc0 built on OS X 10.6
> (bsd.math).  All but one of the runs pass.  The failure:
>
> Run 766 of 1000
> Detected SAGE64 flag
> Building Sage on OS X in 64-bit mode
> sage -t -long -force_lib "devel/sage/sage/libs/fplll/fplll.pyx"
> **********************************************************************
> File
> "/Users/buildbot/build/sage/bsd-2/bsd_64_full/build/sage-4.6.0pre0/devel/sa
> ge/sage/libs/fplll/fplll.pyx", line 853:
>     sage: L.echelon_form() == A.echelon_form()
> Expected:
>     True
> Got:
>     False
> }}}
>
> The error also occurs with a 32-bit build on bsd.math (OS X 10.6, 5 out
> of 1000 runs) and on sage.math (64-bit Ubuntu 8.04.4 LTS, 6 of 1000
> runs).
>
> David Kirkby does '''not''' get any incorrect results on !OpenSolaris
> 06/2009 after more than 15000 runs with 4.6.rc0 and more than 16000 with
> 4.6.1.alpha0. He had a total of 31748 passes. However, he did experience
> 109 doctest failures which are likely to be result of doctesting two
> copies of Sage simultaneously, as these were using the same directory for
> temporary files ({{{$HOME/.sage/tmp}}}). His errors were like  this:
>
> {{{
> Run 442 of 100000
> sage -t -long -force_lib "devel/sage/sage/libs/fplll/fplll.pyx"
> python: can't open file '/export/home/drkirkby/.sage//tmp/fplll.py':
> [Errno 2] No such file or directory
>
>         [0.2 s]
> }}}
>
> and never due to False being return instead of True.

New description:

 Reported on [http://groups.google.com/group/sage-
 devel/browse_thread/thread/145fb7e073d4e12b sage-devel]:
 {{{
 I ran

 ./sage -t -long -force_lib "devel/sage/sage/libs/fplll/fplll.pyx"

 1000 times in serial [1] with a 64-bit 4.6.rc0 built on OS X 10.6
 (bsd.math).  All but one of the runs pass.  The failure:

 Run 766 of 1000
 Detected SAGE64 flag
 Building Sage on OS X in 64-bit mode
 sage -t -long -force_lib "devel/sage/sage/libs/fplll/fplll.pyx"
 **********************************************************************
 File
 "/Users/buildbot/build/sage/bsd-2/bsd_64_full/build/sage-4.6.0pre0/devel/sa
 ge/sage/libs/fplll/fplll.pyx", line 853:
     sage: L.echelon_form() == A.echelon_form()
 Expected:
     True
 Got:
     False
 }}}

 The error also occurs with a 32-bit build on bsd.math (OS X 10.6, 5 out of
 1000 runs) and on sage.math (64-bit Ubuntu 8.04.4 LTS, 6 of 1000 runs).

 David Kirkby does '''not''' get any incorrect results on !OpenSolaris
 06/2009 after more than 15000 runs with 4.6.rc0 and more than 16000 with
 4.6.1.alpha0. He had a total of 31748 passes. However, he did experience
 109 doctest failures which are likely to be result of doctesting two
 copies of Sage simultaneously, as these were using the same directory for
 temporary files ({{{$HOME/.sage/tmp}}}). His errors were like  this:

 {{{
 Run 442 of 100000
 sage -t -long -force_lib "devel/sage/sage/libs/fplll/fplll.pyx"
 python: can't open file '/export/home/drkirkby/.sage//tmp/fplll.py':
 [Errno 2] No such file or directory

         [0.2 s]
 }}}

 and never due to False being return instead of True. His problems are
 probably the result of the issues discussed on #9739.

--

Comment(by drkirkby):

 Replying to [comment:6 leif]:
 > Replying to [comment:5 drkirkby]:
 > > I reckon you Linux and OS X users should upgrade to Solaris!
 > >
 > > Dave
 >
 > What if those failures are ''intended'' by the fplll authors, but just
 do ''not'' work on ''your'' machine / operating system? Or just those
 "file not found" instances would have been the ones failing... Nobody
 knows. ;-)

 I was rather expecting you to have something to say on this;-)

 FWIW, I'm now doctesting again, but this time only testing one instance of
 Sage. So errors due to using the one directory for temp files should not
 exist. I've only managed to run the tests 3723 times, but none of them
 have failed in any way whatsoever.

 I personally think my initial failures were due to #9739.

 I think the matrix used for this test might be random, which could explain
 failures which occur when (for example) all elements are zero. However,
 that would probably not explain why I don't get any failures.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10195#comment:7>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to