This is on amd64 gutsy gibbon:
The following tests failed:
sage -t devel/sage/sage/rings/bernoulli_mod_p.pyx
sage -t devel/sage/sage/rings/arith.py
sage -t devel/sage/sage/interfaces/lisp.py
Total time for all tests: 4005.5 seconds
Please see /home/wdj/sagefiles/sage-
Hi folks,
at #4070 there is now an updated spkg and a patch which should fix all
the known PolyBoRi issues. There are more things to be fixed in other
places, so stay tuned for rc1 later on tonight.
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this group, sen
On Sep 7, 8:57 am, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 7, 8:43 am, mhampton <[EMAIL PROTECTED]> wrote:
>
> > Everything fails for me on OS X 10.5, intel. Every test has the
> > following sort of stuff:
>
>
>
> The above fix also fixes this issue.
>
> > -M. Hampton
>
> *But* at exit we
On Sep 7, 8:43 am, mhampton <[EMAIL PROTECTED]> wrote:
> Everything fails for me on OS X 10.5, intel. Every test has the
> following sort of stuff:
The above fix also fixes this issue.
> -M. Hampton
*But* at exit we get a lot of
python(77859) malloc: *** error for object 0x2b73bf0: Non-al
Everything fails for me on OS X 10.5, intel. Every test has the
following sort of stuff:
File "/Users/mh/sagestuff/sage-3.1.2.rc0/local/lib/python2.5/site-
packages/sage/all_cmdline.py", line 14, in
from sage.all import *
File "/Users/mh/sagestuff/sage-3.1.2.rc0/local/lib/python2.5/site
And the valgrind issue goes away if we link the pbori.pyx statically
with libpolybori.a,libpboriCudd.a and libgroebner.a. To do that delete
all ibpolybori*[so|dylib]*,libpboriCudd.*[so|dylib]* and
libgroebner.*[so|dylib]* and then rebuild sage/rings/polynomial/
pbori.pyx. Then the error is gone:
Sorry for all the noise, but this seems related:
==9379== 1,826,562 (64 direct, 1,826,498 indirect) bytes in 1 blocks
are definitely lost in loss record 10,699 of 14,342
==9379==at 0x4A1C649: operator new(unsigned long)
(vg_replace_malloc.c:230)
==9379==by 0x13DD9B53:
polybori::CDDManager
Ok,
it is the new PolyBoRi:
==671== Invalid read of size 8
==671==at 0x1417F2C4: __tcf_1 (CCuddCore.h:159)
==671==by 0x4FEEB8C: exit (in /lib/libc-2.3.6.so)
==671==by 0x4A6D11: handle_system_exit (pythonrun.c:1620)
==671==by 0x4A6F08: PyErr_PrintEx (pythonrun.c:1064)
==671==b
On Sep 7, 6:44 am, Martin Albrecht <[EMAIL PROTECTED]>
wrote:
> > This one passed every time I tried it separately:
> > sage -t devel/sage/sage/rings/bernoulli_mod_p.pyx
>
> I had the same problem with
>
> http://trac.sagemath.org/sage_trac/ticket/4066
Hmm, I do not see how this could cause t
> This one passed every time I tried it separately:
> sage -t devel/sage/sage/rings/bernoulli_mod_p.pyx
I had the same problem with
http://trac.sagemath.org/sage_trac/ticket/4066
Cheers,
Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_ww
On 64-bit the only problem I had was with interfaces/lisp.py which is known.
On 32-bit there was more:
sage -t devel/sage/sage/stats/hmm/chmm.pyx
sage -t devel/sage/sage/stats/hmm/hmm.pyx
sage -t devel/sage/sage/schemes/elliptic_curves/monsky_washnitzer.py
sage
Two single but different testlong failures on two different hardy
x86_64 boxes. I wacked the local logs and screens before I captured
them to paste here. kinda cashing so here are the links to the
logs...
http://www.tarbox.org/sage/hq2.tar.bz2
http://www.tarbox.org/sage/noc1.tar.bz2
-glenn
O
Oh yeah, my shortlist for 3.1.2.final:
#3476: save timeit information with sage -t -timeit
#3711: notebook -- folder of worksheets not properly saved
#3918: notebook -- MAJOR BUG involving uploading file from URL
#3957: notebook -- major bug in opening notebooks and plots
#4055: serious bug in p
13 matches
Mail list logo
