On Jan 15, 10:54 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> One error in testing (see below):
>
> On Jan 15, 2008, at 12:05 AM, mabshoff wrote:
>
> > Sage 10.2.alpha3 is out. The combinatorics update has been
> > sorted out and doctests should pass. There were also a
> > whole bunch of small updates. The big push for alpha4 [at
> > least on my end] will be the package update and the merging
> > of the 64 bit MacIntel fixes.
>
> > Tarball [199MB] is the usual place at
>
> >http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10/
> > sage-2.10.alpha3.tar
>
> Mac OS X, 10.4.11 (Dual Quad Xeon):
>
> Install succeeded:
>
> real 76m49.526s
> user 63m16.093s
> sys 31m32.407s
>
> Testing had one glitch:
>
> sage -t devel/sage-main/sage/schemes/generic/projective_space.py
> A mysterious error (perphaps a memory error?) occurred, which
> may have crashed d
> octest.
> [11.9 s]
>
> ----------------------------------------------------------------------
> The following tests failed:
>
> sage -t devel/sage-main/sage/schemes/generic/
> projective_space.py
> Total time for all tests: 2743.9 seconds
>
> There was a python crash during the testing, but I'm not at home to
> determine where that might have occurred. I've pushed that crash
> dump to sage.math.washington.edu:~justin/logs/python.log, in case it
> contains interesting stuff. I won't be home to do any more checking
> until late tonight.
>
> Justin
Hi Justin,
I have been seeing non-reproducible doctest failures on OSX for quite
a while now, but so far nobody has had any luck tracking them down and
more importantly fixing them. The failures themselves always seem to
be caused on exit, i.e. there are never any "wrong" results being
printed. I suspect that it is caused by #1337, i.e. "tp_new leads to
munmap_chunk(): invalid pointer segfault". It causes a segfault on
every exit on Linux/PPC. There was a patch on cython-dev about a week
ago named "Re: [Cython-dev] fix for tp_clear()" [sorry, no link since
the archives are list members only - I don't know why] - which seems
at least related. The ticket was never updated by me with the latest
info, but that segfault is caused by line 2200 in structure/
element.pyx:
# This is pretty nasty low level stuff. The idea is to speed up
construction
# of EuclideanDomainElements (in particular Integers) by skipping some
tp_new
# calls up the inheritance tree.
PY_SET_TP_NEW(EuclideanDomainElement, Element)
in my opinion. I haven't had time to fix it yet and I didn't feel like
bothering Robert about it during the last couple weeks.
>
> --
> Justin C. Walker, Curmudgeon-At-Large
> Institute for the Absorption of Federal Funds
Cheers,
Michael
> --------
> If you're not confused,
> You're not paying attention
> --------
--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
