On Thu, Nov 6, 2008 at 7:09 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> On Thu, Nov 6, 2008 at 12:52 PM, Franco Saliola <[EMAIL PROTECTED]> wrote:
>>
>> Hello David,
>>
>> On Thu, Nov 6, 2008 at 1:51 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>>
>>> With amd64 intrepid ibex, it builds fine but sage -testall
>>> seems to have the same locking-up issues as with the alpha2 version.
>>
>> I'm too am using amd64 intrepid ibex and having the same issues.
>>
>> The following doctests fail for me (and maybe others, the tests are
>> still running). But can you test whether these fail for you as well?
>
>
> Nope.
>
> Here's the test
>
> [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]
>
> ----------------------------------------------------------------------
> All tests passed!
> Total time for all tests: 11.9 seconds
>
> and here are some command-line tests:
>
>
> [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.
Thanks for checking. I am mystified too.
Other than a few hangs during testall, all tests besides lisp.py
passed. Which was unexpected because I thought other code that relies
on lisp.py would fail as well.
Franco
--
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
