On Nov 7, 6:13 am, mhampton <[EMAIL PROTECTED]> wrote:
> I just had one timeout failure on a PPC mac running 10.4, on modular/
> abvar/homspace.py, plus the following malloc error which didn't cause
> the test to fail but maybe its worth noting:
>
> sage -t devel/sage/sage/libs/pari/gen.pyx
> python(5728) malloc: *** vm_allocate(size=4096000000) failed (error
> code=3)
> python(5728) malloc: *** error: can't allocate region
> python(5728) malloc: *** set a breakpoint in szone_error to debug
Yeah, the above is a known error (the printing of crap) and there
already is a ticket for it.
> sage -t devel/sage/sage/modular/abvar/homspace.py *** ***
> Error: TIMED OUT! *** ***
> *** *** Error: TIMED OUT! *** ***
> [443.8 s]
Please open a ticket for this so that we mark some tests as "#long
time"
> (Total time for all tests: 13549.5 seconds)
>
> -Marshall
Cheers,
Michael
> On Nov 6, 9:51 pm, mhampton <[EMAIL PROTECTED]> wrote:
>
> > All tests passed on my intel mac, running 10.4. I am building and
> > testing on a PPC 10.4 as well, but I won't be awake when that
> > finishes.
>
> > -Marshall
>
> > On Nov 6, 9:41 pm, Dan Drake <[EMAIL PROTECTED]> wrote:
>
> > > On Thu, 06 Nov 2008 at 01:09PM -0500, David Joyner wrote:
> > > > [EMAIL PROTECTED]:~/sagefiles/sage-3.2.alpha3$ ./sage -t
> > > > devel/sage/sage/interfaces/lisp.py
> > > > sage -t devel/sage/sage/interfaces/lisp.py
> > > > [11.8 s]
>
> > > I'm using Intrepid amd64 and get the same failures as Franco.
>
> > > > [EMAIL PROTECTED]:~/sagefiles/sage-3.2.alpha3$ ./sage
> > > > ----------------------------------------------------------------------
> > > > | Sage Version 3.2.alpha3, Release Date: 2008-11-05 |
> > > > | Type notebook() for the GUI, and license() for information. |
> > > > ----------------------------------------------------------------------
>
> > > > sage: sage: lisp.eval('(* 4 5)')
> > > > '20'
> > > > sage: sage: lisp.eval('(+ 2 2)')
> > > > '4'
> > > > sage: lisp(0).bool()
> > > > False
> > > > sage:
>
> > > > They are as expected.
>
> > > > I am mystified by the failures.
>
> > > Here's what I get when I do that:
>
> > > ----------------------------------------------------------------------
> > > | Sage Version 3.2.alpha3, Release Date: 2008-11-05 |
> > > | Type notebook() for the GUI, and license() for information. |
> > > ----------------------------------------------------------------------
>
> > > sage: lisp.eval('(* 4 5)')
> > > '(* 4 5)\n20'
> > > sage: lisp.eval('(+ 2 2)')
> > > '(+ 2 2)\n4'
> > > sage: lisp(0).bool()
> > > True
>
> > > As Georg said, it's some sporadic Lisp/Maxima thing that we're hoping is
> > > fixed by switching to a different Lisp.
>
> > > Dan
>
> > > --
> > > --- Dan Drake <[EMAIL PROTECTED]>
> > > ----- KAIST Department of Mathematical Sciences
> > > ------- http://mathsci.kaist.ac.kr/~drake
>
> > > signature.asc
> > > < 1KViewDownload
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
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://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
