Build ok but --testall still stalling here (using PBUILD):

sage -t  devel/sage/sage/dsage/tests/testdoc.py

[EMAIL PROTECTED] -a
Linux host-57-71 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC
2007 x86_64 x86_64 x86_64 GNU/Linux
[EMAIL PROTECTED] | grep SAGE
SAGE_BUILD_THREADS=2
SAGE_PBUILD=yes

John

2008/5/4 mabshoff <[EMAIL PROTECTED]>:
>
>  Here we go with 3.0.1.final. pbuild should work, but there
>  is still a known failure while doctesting (see #3098). 3.0.1
>  official sources will be rolled out in a couple hours and
>  binaries should follow tomorrow. The official announcement
>  will go out once we have binaries and mirrored them out.
>
>  Sources & binaries in the usual space, i.e. check out
>
>  http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.1/
>
>  Cheers,
>
>  Michael
>
>  Merged in final:
>
>  #3010: Michael Abshoff: Numerical noise doctest failure in
>        rings/complex_double.pyx
>  #3085: Jason Grout: fix identity matrix docs
>  #3087: Tim Abbott: Fix stupid mistakes in Debian palp copyright
>        files
>  #3088: Tim Abbott: Fixes for Debian gfan build
>  #3092: Tim Abbott: Debian Singular permissions fixes
>  #3093: Tim Abbott: Debian lcalc package missing -DINCLUDE_PARI
>        flag
>  #3094: Tim Abbott: Update to SAGE Debian packaging
>  #3095: Lars Fischer, Michael Abshoff: Notebook, Documentation
>        of DATA has a small error
>  #3096: Michael Abshoff: Fix documentation rebuild issues for
>        Sage 3.0.1.final
>  #3098: Willem Jan Palenstijn, William Stein: doctest failure
>        in devel/sage/sage/rings/ring.pyx
>  #3101: Gary Furnish, Michael Abshoff: pbuild: mwrank.so needs
>        to be build as a C++ extension
>  >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to