Hi Paulo, > 2011/1/27 François Bissey <francois.bis...@canterbury.ac.nz>: > > Hi all, > > I am delaying a Mandriva sagemath 4.6.1 due to related reasons, > and may not release it if sagemath 4.6.2 is released soon :-). Since > Mandriva cooker is using python 2.7.1 and cython 0.14, I needed to > use a custom cython 0.13, but am trying to correct some issues with > python, to use python 2.7.1. > > > Just adding unittest.py from python2.6 to PYTHONPATH, that points > to /usr/share/sage/site-packages corrected like 90% of the problems, > but just now I got this one in > sage/rings/polynomial/polynomial_quotient_ring_element.py > > [[ cut&paste of test case in sage under a python in gdb > slightly different than sage -gdb, but effectively the same ]] > -%<- > sage: R.<x> = PolynomialRing(QQ) > sage: sage: S.<a> = R.quotient(x^3-2) > sage: sage: int(S(10)) > 10 > sage: int(a) > Fatal Python error: GC object already tracked > > Program received signal SIGABRT, Aborted. > [...] > 0x00007ffff74c4075 in raise () from /lib64/libc.so.6 > (gdb) bt > #0 0x00007ffff74c4075 in raise () from /lib64/libc.so.6 > #1 0x00007ffff74c5806 in abort () from /lib64/libc.so.6 > #2 0x00007ffff7b1c9de in Py_FatalError (msg=<value optimized out>) > at Python/pythonrun.c:1670 > #3 0x00007ffff7a8c76e in PyFrame_New (tstate=0x6020a0, > code=<value optimized out>, globals=0x998f50, locals=<value optimized > out>) at Objects/frameobject.c:742 > #4 0x00007ffff7b00d67 in PyEval_EvalCodeEx (co=0x95f5b0, > globals=<value optimized out>, locals=<value optimized out>, args= > 0x2265e08, argcount=4, kws=0x2265e28, kwcount=0, defs=0x814d28, > defcount= 5, closure=0x0) at Python/ceval.c:3032 > #5 0x00007ffff7aff835 in fast_function (f=<value optimized out>, > throwflag=<value optimized out>) at Python/ceval.c:4108 > #6 call_function (f=<value optimized out>, throwflag=<value optimized > out>) at Python/ceval.c:4033 > [...] > > > so it's that time again where I look at how "easy" it would be to update > > various pieces of sage to the latest upstream. The tests were performed > > on a linux machine running in 64 bit (amd64) based on 4.6.2.alpha2. > > We haven't made the leap to python-2.7 yet.
> > numpy-1.5.1: upgrade quite nicely, just two doctests broken by a new > > warning from numpy: > > sage -t -force_lib "devel/sage/sage/calculus/interpolators.pyx" > > ********************************************************************** > > File > > "/home/gnuke/gentoo/usr/share/sage/devel/sage/sage/calculus/interpolators > > .pyx", line 52: > > sage: m = Riemann_Map([lambda x: ps.value(x)], [lambda x: > > ps.derivative(x)],0) > > Expected nothing > > Got: > > doctest:1: ComplexWarning: Casting complex values to real discards the > > imaginary part > > ********************************************************************** > > I see these too, but like this: > > sage -t -force_lib > "/usr/lib64/python2.7/site-packages/sage/calculus/interpolators.pyx" > [?1034hWarning: invalid value encountered in divide > Warning: invalid value encountered in divide > <<<<<< last line repeats at least more 300 times >>>>>> > ********************************************************************** > File "/usr/lib64/python2.7/site-packages/sage/calculus/interpolators.pyx", > line 52: > sage: m = Riemann_Map([lambda x: ps.value(x)], [lambda x: > ps.derivative(x)],0) > Expected nothing > Got: > doctest:1: ComplexWarning: Casting complex values to real discards > the imaginary part > OK, I skipped the bit about "Warning: invalid value encountered in divide" because it is not technically part of the failure. It started to appear with cython-0.13, and doesn't make the tests fail because it is actually std-err I believe. > A good share of packages I only update when sagemath updates, > but other packages are updated by other people, or, I myself would > update to latest upstream, but in the case of sage, I would first > test... > > I also get a massive number of rounding ones, like: > -%<- > File "/usr/share/sage/devel/sage/sage/finance/time_series.pyx", line 1550: > sage: v.variance() > Expected: > 0.80000000000000004 > Got: > 0.8 > -%<- We got some in time_series.pyx although not that particular one, some results are very picky in regards to blas/cblas/lapack. A summary of what happens to us but that we consider harmless is here: https://github.com/cschwan/sage-on-gentoo/wiki/Known-test-failures A list of our "problems" that could also be consulted is here: https://github.com/cschwan/sage-on-gentoo/issues > > File "/usr/share/sage/devel/sage/sage/finance/markov_multifractal.py", line > 99: sage: msm.m0() > Expected: > 1.3999999999999999 > Got: > 1.4 > -%<- > File > "/usr/share/sage/devel/sage/sage/schemes/elliptic_curves/ell_rational_fiel > d.py", line 2134: > sage: F.CPS_height_bound() > Expected: > 0.65551583769728516 > Got: > 0.6555158376972852 > -%<- > I do not see these at the moment. By the way our tip about pari unfortunately didn't help with https://github.com/cschwan/sage-on-gentoo/issues#issue/40 that's a shame. Francois -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
