Hi,
I'm not sure what has been reported so far regarding building rc1, but here
are some failures.
On OSX 10.5 these fail:
sage -t -long devel/sage/sage/crypto/mq/sr.py
sage -t -long devel/sage/sage/interfaces/lisp.py
sage -t -long devel/sage/sage/matrix/matrix_real_double_dense.pyx
sage -t -long
devel/sage/sage/schemes/elliptic_curves/ell_finite_field.py
sage -t -long devel/sage/sage/schemes/elliptic_curves/period_lattice.py
On sage.math this fails:
sage -t -long devel/sage/sage/interfaces/maxima.py
On my 32-bit debian test vmware image these all fail:
sage -t -long devel/sage/sage/matrix/matrix_real_double_dense.pyx
sage -t -long devel/sage/sage/stats/hmm/hmm.pyx
sage -t -long devel/sage/sage/stats/hmm/chmm.pyx
sage -t -long devel/sage/sage/dsage/dist_functions/dist_factor.py
sage -t -long devel/sage/sage/schemes/elliptic_curves/period_lattice.py
sage -t -long devel/sage/sage/crypto/mq/sr.py
On the 64-bit image only the sr.py one fails (lack of memory).
On arch linux these two fail:
sage -t -long devel/sage/sage/crypto/mq/sr.py
sage -t -long devel/sage/sage/interfaces/psage.py
On OSX 10.5 ppc (Clement Pernet's office computer), the doctests
hang here forever (for at least one day):
sage -t -long devel/sage/sage/interfaces/lisp.py
(hangs forever)
Only this fails on iras/itanium:
sage -t -long devel/sage/sage/matrix/matrix_real_double_dense.pyx
sage -t -long devel/sage/sage/stats/hmm/chmm.pyx
sage -t -long devel/sage/sage/stats/hmm/hmm.pyx
On Wed, Sep 10, 2008 at 9:14 AM, Georg S. Weber
<[EMAIL PROTECTED]> wrote:
>
> status report for OS X 10.4 / Xcode 2.4.1 (the same on two machines),
> building
> - Sage 3.1.2rc1
> with two spkgs replaced:
> - libm4ri-20080909.spkg
> - polybori-0.5rc.p5.spkg
> (the other pending patches for rc2 were not applied):
>
>
> PowerPC 550MHz:
> Builds successful, yeah! (The doctests were just started, and will run
> overnight)
>
>
> Intel Core2 Duo 2.0 GHz:
> Builds successful, yeah!
>
> However the build time for this box was four hours as compared to two
> hours for building Sage 3.1.1 on the same box.
> It looks like as if the 3.1.2rc1 build was done only on one of the two
> cores of the CPU?!
>
> Doctests just finished and show some reported (John) and two or three
> other failures (to whom shall I assign tickets?),
> which are of minor importance except possibly for the following issue:
> The doctests for 3.1.2rc1 also took twice the time than the doctests
> for 3.1.1 did
> (11181.7 seconds compared to 5673.2 seconds).
> And consequently, the 3.1.2.rc1 doctest for psage.py failed (it had
> worked for 3.1.1):
>
>
> ...
> sage -t devel/sage/sage/interfaces/povray.py
> [5.2 s]
> sage -t devel/sage/sage/interfaces/psage.py End Of
> File (EOF) in read_nonblocking(). Empty string style platform.
> <pexpect.spawn instance at 0xca519e0>
> version: 2.0 ($Revision: 1.151 $)
> command: /Users/georgweber/Public/sage/sage-3.1.2.rc1-src2/sage
> args: ['/Users/georgweber/Public/sage/sage-3.1.2.rc1-src2/sage']
> patterns:
> sage:
> buffer (last 100 chars):
> before (last 100 chars):
> after: <class 'pexpect.EOF'>
> match: None
> match_index: None
> exitstatus: None
> flag_eof: 1
> pid: 27671
> child_fd: 7
> timeout: 30
> delimiter: <class 'pexpect.EOF'>
> logfile: None
> maxread: 100000
> searchwindowsize: None
> delaybeforesend: 0
>
> [27.9 s]
> sage -t devel/sage/sage/interfaces/qepcad.py
> [7.9 s]
> ...
>
>
> Cheers,
> gsw
>
> >
>
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
