sage-5.1.rc0 released

[Jeroen Demeyer]

Dear Sage lovers,

We're releasing Sage 5.1.rc0.

Source archive:

http://boxen.math.washington.edu/home/release/sage-5.1.rc0/sage-5.1.rc0.tar

Upgrade path:

http://boxen.math.washington.edu/home/release/sage-5.1.rc0/sage-5.1.rc0/

The source and upgrade path can also be found on the mirror network
(you might need to wait a while before the mirrors are synchronized):

http://www.sagemath.org/download-latest.html


Please build, test, and report! We'd love to hear about your
experiences with this release.

== Tickets ==

* We closed 207 tickets in this release. For details, see

http://boxen.math.washington.edu/home/release/sage-5.1.rc0/tickets.html

Closed tickets:

#8073: deprecation version number should say "After version ..."
[Reviewed by Volker Braun, Karl-Dieter Crisman]
#8546: add section on deprecating functions to developer's guide
[Reviewed by Volker Braun]
#12214: polygon documentation in error [Reviewed by Karl-Dieter Crisman]

Merged in sage-5.1.rc0:

#1172: Keshav Kini: change the watkins license in SAGE_ROOT/COPYING
[Reviewed by R. Andrew Ohana]
#9544: Peter Jeremy, Jeroen Demeyer: Fix flintqs on FreeBSD [Reviewed by
Stephen Montgomery-Smith, Jeroen Demeyer, Karl-Dieter Crisman]
#12855: Jeroen Demeyer: FLINTQS fails to build on Solaris (with GCC
4.7.x) [Reviewed by Karl-Dieter Crisman]
#13152: John Palmieri: add vsyasm, yasm, and ytasm to .hgignore
[Reviewed by Jeroen Demeyer]

[Volker Braun]

On Thursday, June 28, 2012 2:21:13 PM UTC+1, Jeroen Demeyer wrote:

#8073: deprecation version number should say "After version ..."
[Reviewed by Volker Braun, Karl-Dieter Crisman]
#8546: add section on deprecating functions to developer's guide
[Reviewed by Volker Braun]

Note that we only closed old tickets that are superseded by the new deprecation decorator. The actual ticket still needs review, and it would be great if somebody could do that before it bitrots: 

http://trac.sagemath.org/sage_trac/ticket/13109

[Justin C. Walker]

On Jun 28, 2012, at 06:21 , Jeroen Demeyer wrote:

> Dear Sage lovers,
>
> We're releasing Sage 5.1.rc0.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-5.1.rc0/sage-5.1.rc0.tar

Built from scratch on Mac OS X 10.6.8 and 10.7.4. No problems, and all tests passed, on both systems!

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Director
Institute for the Enhancement of the Director's Income
--------
"Weaseling out of things is what separates us from the animals.
Well, except the weasel."
- Homer J Simpson
--------

[Michael Welsh]

On 29/06/2012, at 1:21 AM, Jeroen Demeyer wrote:
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.

Built on OS X 10.7.4 (with XCode 4.3.2, I'm about to upgrade) and all tests passed.

[leif]

Justin C. Walker wrote:
>
> On Jun 28, 2012, at 06:21 , Jeroen Demeyer wrote:
>
>> Dear Sage lovers,
>>
>> We're releasing Sage 5.1.rc0.
>>
>> Source archive:
>>
>> http://boxen.math.washington.edu/home/release/sage-5.1.rc0/sage-5.1.rc0.tar
>
> Built from scratch on Mac OS X 10.6.8 and 10.7.4. No problems, and all tests passed, on both systems!

Also built fine from scratch and passed all tests on Ubuntu 10.04.4 LTS
x86_64 (GCC 4.4.3), although -- for whatever reason -- ptestlong took
35%(!) longer than for e.g. beta2, on an otherwise idle machine.

Did anybody else observe such (with one of the recent devel releases)?


-leif

--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail

[Justin C. Walker]

Not in my case (10.6.8, Dual 6-core Xeons). The 5.1 series of releases show a decrease from ~3000 tests (B0,B1) to ~2100 tests (B2,B5,B6,RC0). The timing in all cases was ~10-11 minutes.

I see similar behavior on 10.7.4 (4-core Core i7).

Justin

--
Justin C. Walker

Director
Institute for the Enhancement of the Director's Income
--

Fame is fleeting, but obscurity
just drags on and on. F&E

[Anthony David]

lsb_release -a

LSB Version:    core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch

Distributor ID: Ubuntu

Description:    Ubuntu 11.10

Release:        11.10

Codename:       oneiric

Built OK

----------------------------------------------------------------------

The following tests failed:

        sage -t  -long -force_lib "devel/sage/sage/misc/randstate.pyx" # Time out

        sage -t  -long -force_lib "devel/sage/sage/misc/sagedoc.py"

        sage -t  -long -force_lib "devel/sage/sage/interacts/debugger.py" # Time out

        sage -t  -long -force_lib "devel/sage/sage/interfaces/expect.py" # Time out

        sage -t  -long -force_lib "devel/sage/sage/interfaces/sage0.py" # Time out

        sage -t  -long -force_lib "devel/sage/sage/interfaces/psage.py" # Time out

        sage -t  -long -force_lib "devel/sage/sage/rings/polynomial/pbori.pyx"

        sage -t  -long -force_lib "devel/sage/sage/modules/free_module.py"

        sage -t  -long -force_lib "devel/sage/sage/tests/startup.py" # Time out

Total time for all tests: 31644.5 seconds

1GB RAM, 2GB swap. two failures due to VM exhaustion.

Regards

Anthony David

--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To post to this group, send email to sage-r...@googlegroups.com.
To unsubscribe from this group, send email to sage-release...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sage-release?hl=en.

[leif]

You can set SAGE_TIMEOUT (for 'make [p]test' etc.) or SAGE_TIMEOUT_LONG
(for 'make [p]testlong' etc.) to avoid "regular" timeouts on slower
machines; default is 1800 (seconds) for the latter IIRC. Note that all
timings are wall time, not CPU time, so it also makes sense to increase
them on a fast but busy machine (and/or if you're using more threads
than the machine has cores, although that doesn't make much sense if
you're short of available RAM anyway).

[Tim Joseph Dumol]

--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To post to this group, send email to sage-r...@googlegroups.com.
To unsubscribe from this group, send email to sage-release...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sage-release?hl=en.

Built from scratch on Arch Linux x64. Had this test fail:

**********************************************************************

File "/opt/sage/devel/sage/sage/schemes/plane_curves/curve.py", line 122:

    sage: C.geometric_genus()

Exception raised:

    Traceback (most recent call last):

      File "/opt/sage/local/bin/ncadoctest.py", line 1231, in run_one_test

        self.run_one_example(test, example, filename, compileflags)

      File "/opt/sage/local/bin/sagedoctest.py", line 38, in run_one_example

        OrigDocTestRunner.run_one_example(self, test, example, filename, compileflags)

      File "/opt/sage/local/bin/ncadoctest.py", line 1172, in run_one_example

        compileflags, 1) in test.globs

      File "<doctest __main__.example_6[9]>", line 1, in <module>

        C.geometric_genus()###line 122:

    sage: C.geometric_genus()

      File "/opt/sage/local/lib/python/site-packages/sage/schemes/plane_curves/curve.py", line 141, in geometric_genus

        self.__genus = self.defining_ideal().genus()

      File "/opt/sage/local/lib/python/site-packages/sage/rings/polynomial/multi_polynomial_ideal.py", line 602, in __call__

        return self.f(self._instance, *args, **kwds)

      File "/opt/sage/local/lib/python/site-packages/sage/rings/polynomial/multi_polynomial_ideal.py", line 1745, in genus

        self.__genus = Integer(genus(self))

      File "function.pyx", line 1249, in sage.libs.singular.function.SingularFunction.__call__ (sage/libs/singular/function.cpp:11542)

      File "function.pyx", line 1439, in sage.libs.singular.function.call_function (sage/libs/singular/function.cpp:13049)

    RuntimeError: Error in Singular function call 'genus':

     delta not found, please inform the authors

     leaving normal.lib::deltaP

     leaving normal.lib::genus

**********************************************************************

But I couldn't get the test to fail again:

$ for i in {1..100}; do sage -t devel/sage/build/sage/schemes/plane_curves/curve.py; done

[all passed]

Yours,
Tim Dumol