Sage 4.6.alpha1 released

[Mitesh Patel]

Hi,

We've unleashed Sage 4.6.alpha1.

Source archive:

http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1.tar

Upgrade path:

http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1/

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

== Known problems ==

* The long doctests pass for me on redhawk, sage, and t2.math. See
#9926 for a failure on bsd.math (32-bit build, OS X 10.6).

* The tests also pass on the Skynet cluster, except for cleo and iras
(both Itanium), where PARI fails to build. This is #9897.

* Builds with 'export SAGE_PARALLEL_SPKG_BUILD=yes' could fail with the
Singular package. This is #9946.

The full list of blockers is at

http://trac.sagemath.org/sage_trac/query?priority=blocker&group=status&groupdesc=1&milestone=sage-4.6

Feel free to comment, patch, and review.

== Tickets ==

Closed:

#9768: Alexander Dreyer: Fix PolyBoRi's broken dynamic libraries
[Reviewed by Martin Albrecht]
#9837: Leif Leonhardy, Jeroen Demeyer: Bug in MPIR 2.1.1 in
mpz_divexact() [Reviewed by Leif Leonhardy, Jeroen Demeyer]

Merged in sage-4.6.alpha1:

#783: Mike Hansen: dilog is lame [Reviewed by Paul Zimmermann]
#1431: Jason Grout, Karl-Dieter Crisman: basic plotting: add support for
setting the location and labels of all tick marks on the x and y axes
[Reviewed by Karl-Dieter Crisman]
#6934: Jason Grout: Fix eigenvectors (and a lot of other stuff) for
symbolic matrices [Reviewed by Rob Beezer]
#6938: Karl-Dieter Crisman: sage-README-osx.txt is non-sensical for a
source distribution. [Reviewed by John Palmieri]
#7154: Ryan Grout: options for point/arrow thickness are inconsistently
named [Reviewed by Jason Grout]
#7199: Yann Laigle-Chapuy: inefficiency of creation of sparse matrices
[Reviewed by Paul Zimmermann]
#8838: Ryan Grout: make "arrow()" take 3d vectors [Reviewed by Jason Grout]
#8950: Oriol Castejon: new function for sage.calculus.desolve module
[Reviewed by Burcin Erocal, Pablo Angulo, Marshall Hampton]
#9076: Vincent Delecroix: plot Arc of circle and ellipse [Reviewed by
Karl-Dieter Crisman]
#9199: Ryan Grout: plot(..., fill=False) still turns on filling
[Reviewed by Jason Grout]
#9200: Dana Ernst, Burcin Erocal: Add left and right directions to
limits [Reviewed by Rob Beezer]
#9203: Vincent Delecroix: plot ellipses [Reviewed by Karl-Dieter Crisman]
#9296: Volker Braun: Add lattice computations for convex polyhedral
cones [Reviewed by Andrey Novoseltsev]
#9315: William Stein: sage-4.4.3, 4.4.4: Basic pickling bug in finite
fields [Reviewed by John Cremona]
#9330: Chris Wuthrich: Documentation for sha_tate.py not quite looking
right [Reviewed by Karl-Dieter Crisman]
#9337: Volker Braun: Add toric divisors [Reviewed by Andrey Novoseltsev]
#9350: Nathann Cohen: Python max flow method [Reviewed by Dmitrii
Pasechnik, David Joyner]
#9395: Paul Zimmermann, Yann Laigle-Chapuy: new doctest for french book
about Sage [Reviewed by Yann Laigle-Chapuy, Paul Zimmermann]
#9400: William Stein, Jeroen Demeyer: modify the NumberField constructor
to pass in optional integer B such that all the internal pari routines
will replace the discriminant by its gcd with B, making some things
massively faster. [Reviewed by Jeroen Demeyer, John Cremona]
#9413: Chris Wuthrich: Bug in tamagawa_product_bsd for elliptic curves
over QQ [Reviewed by John Cremona]
#9443: Niles Johnson: infinite polynomial ring is_integral_domain and
is_field omit optional argument 'proof' [Reviewed by Simon King]
#9502: Andrey Novoseltsev: Basis parent bug in FreeModule [Reviewed by
Volker Braun]
#9504: Andrey Novoseltsev: Add support for toric sublattices [Reviewed
by Volker Braun]
#9603: David Kirkby, Leif Leonhardy: Build iconv in parallel, install it
on HP-UX and make it work properly on Solaris 64-bit. [Reviewed by Peter
Jeremy, Leif Leonhardy, David Kirkby]
#9650: Joris Vankerschaver: Adding support for differential forms
[Reviewed by Niles Johnson]
#9652: Maarten Derickx: Unnecesary and buggy code in arith.py [Reviewed
by Marco Streng, John Cremona, Luis Felipe Tabera]
#9674: Yann Laigle-Chapuy: fix SBox __init__ (again) [Reviewed by Martin
Albrecht]
#9676: Ed Scheinerman: Random Tree constructor for graphs section
[Reviewed by Nathann Cohen]
#9684: Pin-Hung Kao, Armin Straub, Charlie Turner: Make use of
_tidy_model() optional [Reviewed by John Cremona]
#9687: Rob Beezer: Update citation info for Tower of Hanoi graph
generator [Reviewed by Billy Wonderly]
#9696: Rob Beezer: Add methods to AdditiveAbelianGroup [Reviewed by John
Cremona]
#9709: Richard Lindner: Crypto lattice basis generator (update)
[Reviewed by Martin Albrecht]
#9720: Billy Wonderly: Add random echelonizable matrices to
matrix/constructor.py [Reviewed by David Joyner]
#9733: Alexander Dreyer, Fran�ois Bissey: Parallel build of Singular
3-1-1-4-package fails in rare case [Reviewed by Mitesh Patel, Leif
Leonhardy, David Kirkby]
#9741: Rob Beezer: Sorting vertices of a graph [Reviewed by Nathann Cohen]
#9742: Rob Beezer: Sorting edges of a graph [Reviewed by Nathann Cohen]
#9749: Alex Ghitza: huge performance regression in computing with level
one modular forms [Reviewed by William Stein]
#9754: Billy Wonderly: Add random unimodular and subspaces matrices to
matrix/constructor.py [Reviewed by David Joyner, Rob Beezer]
#9771: Niles Johnson: update instructions for reviewers, especially for
new developers [Reviewed by Minh Van Nguyen]
#9776: Mike Hansen: Cygwin: GLPK extension module needs to be more
explicit in its linking [Reviewed by Nathann Cohen]
#9782: Andrey Novoseltsev: Enhanced fans fail for complicated cases
[Reviewed by Volker Braun]
#9784: Dan Drake: list_plot should accept dictionaries [Reviewed by
Jason Grout]
#9802: Billy Wonderly: Add random diagonalizable matrix to
matrix/constructor.py [Reviewed by David Joyner]
#9803: Rob Beezer: Generalize and document the random_matrix constructor
[Reviewed by David Joyner, Mike Hansen]
#9804: David Kirkby: Remove unnecessary dependency for cliquer in
spkg/standard/deps [Reviewed by Leif Leonhardy]
#9810: Andrey Novoseltsev: Heisenbug in RationalPolyhedralCone.facets
[Reviewed by Volker Braun]
#9812: Andrey Novoseltsev: Sorting bug in fan subdivision [Reviewed by
Volker Braun]
#9813: Jason Grout: parametric plot and polar plot aspect ratio
[Reviewed by Dan Drake]
#9816: John Cremona: Elliptic Curves over RR or CC have wrong type
[Reviewed by Chris Wuthrich]
#9836: Nathann Cohen: Linear Programming Thematic Tutorial [Reviewed by
Minh Van Nguyen]
#9839: Andrey Novoseltsev: Add dual cone computation [Reviewed by Volker
Braun]
#9851: Simon King: sage -pkg may hang if there are many uncommitted
changes in the package [Reviewed by Mitesh Patel]
#9852: Nathann Cohen: Error in edge_cut [Reviewed by Dmitrii Pasechnik]
#9859: Leif Leonhardy: Doctest failures due to hard-coded line numbers
in (doctests of) sage/rings/*.pyx [Reviewed by Minh Van Nguyen]
#9861: Nathann Cohen, Minh Van Nguyen: Improving the Graph Theory table
of contents [Reviewed by Minh Van Nguyen]
#9862: Nathann Cohen: Reimplementation of IntervalGraph to handle
repeated vertices. [Reviewed by Ed Scheinerman]
#9871: David Kirkby, Leif Leonhardy: Change Cliquer compiler flags on
Solaris to build without text relocations. [Reviewed by Leif Leonhardy,
John Palmieri]
#9872: Alexander Dreyer: PolyBoRi incorrectly reports a GNU linker is
used with gcc and produces libraries with text relocations. [Reviewed by
David Kirkby]
#9916: Leif Leonhardy: Change Shafarevich-Tate in BSD,
ell_rational_field and padic_lseries (also fixes doctests) [Reviewed by
Mitesh Patel]
#9924: Alex Ghitza: Doctest error in sage/geometry/polyhedra.py
[Reviewed by Andrey Novoseltsev]

[leif]

Mitesh Patel wrote:
> We've unleashed Sage 4.6.alpha1.
>
> Source archive:
>
> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1.tar
>
> Upgrade path:
>
> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1/
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
>
> == Known problems ==
>
> * The long doctests pass for me on redhawk, sage, and t2.math. See
> #9926 for a failure on bsd.math (32-bit build, OS X 10.6).
>
> * The tests also pass on the Skynet cluster, except for cleo and iras
> (both Itanium), where PARI fails to build. This is #9897.
>
> * Builds with 'export SAGE_PARALLEL_SPKG_BUILD=yes' could fail with the
> Singular package. This is #9946.
>
> The full list of blockers is at
>
> http://trac.sagemath.org/sage_trac/query?priority=blocker&group=status&groupdesc=1&milestone=sage-4.6
>

> Feel free to comment, patch, and review. [...]

Ubuntu 10.04 x86_64 (Core2, gcc 4.4.3, native code, O3):

make build: OK (parallel build from scratch, 32 jobs)
make doc: OK (no errors, no warnings)
make ptestlong: OK (all tests passed; 4 threads)

32-bit build(s) in progress...

Just for the record: (At least) ATLAS fails to build with MAKE="make -j"
(i.e. "infinitely" many jobs). This never worked since parallel builds
of ATLAS aren't properly disabled; I'll open a ticket with a patch
fixing that soon...

-Leif

[leif]

leif wrote:
> Mitesh Patel wrote:
>> We've unleashed Sage 4.6.alpha1.
>>
>> Source archive:
>>
>> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1.tar
>>
>> Upgrade path:
>>
>> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1/
>>
>> Please build, test, and report! We'd love to hear about your
>> experiences with this release.
>>
>> == Known problems ==
>>
>> * The long doctests pass for me on redhawk, sage, and t2.math. See
>> #9926 for a failure on bsd.math (32-bit build, OS X 10.6).
>>
>> * The tests also pass on the Skynet cluster, except for cleo and iras
>> (both Itanium), where PARI fails to build. This is #9897.
>>
>> * Builds with 'export SAGE_PARALLEL_SPKG_BUILD=yes' could fail with the
>> Singular package. This is #9946.
>>
>> The full list of blockers is at
>>
>> http://trac.sagemath.org/sage_trac/query?priority=blocker&group=status&groupdesc=1&milestone=sage-4.6
>>
>> Feel free to comment, patch, and review. [...]
>
> Ubuntu 10.04 x86_64 (Core2, gcc 4.4.3, native code, O3):
>
> make build: OK (parallel build from scratch, 32 jobs)
> make doc: OK (no errors, no warnings)
> make ptestlong: OK (all tests passed; 4 threads)
>
>
> 32-bit build(s) in progress...

Ubuntu 9.04 x86 (P4 Prescott, gcc 4.3.3, native code, O3, sse):

make build: OK (parallel build from scratch, 8 jobs)

make doc: OK (no errors, no warnings)
make ptestlong: OK (all tests passed; 4 threads)

-Leif

P.S.: I get (grep "regular file" install.log):

package init file 'sympy/concrete/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/core/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/functions/combinatorial/tests/__init__.py' not
found (or not a regular file)
package init file 'sympy/functions/elementary/tests/__init__.py' not
found (or not a regular file)
package init file 'sympy/functions/special/tests/__init__.py' not found
(or not a regular file)
package init file 'sympy/galgebra/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/geometry/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/integrals/tests/__init__.py' not found (or not
a regular file)
package init file 'sympy/matrices/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/ntheory/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/parsing/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/physics/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/plotting/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/polys/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/printing/pretty/tests/__init__.py' not found
(or not a regular file)
package init file 'sympy/printing/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/series/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/simplify/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/slow_tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/solvers/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/statistics/tests/__init__.py' not found (or not
a regular file)
package init file 'sympy/test_external/__init__.py' not found (or not a
regular file)
package init file 'sympy/utilities/tests/__init__.py' not found (or not
a regular file)
package init file 'sympy/concrete/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/core/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/functions/combinatorial/tests/__init__.py' not
found (or not a regular file)
package init file 'sympy/functions/elementary/tests/__init__.py' not
found (or not a regular file)
package init file 'sympy/functions/special/tests/__init__.py' not found
(or not a regular file)
package init file 'sympy/galgebra/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/geometry/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/integrals/tests/__init__.py' not found (or not
a regular file)
package init file 'sympy/matrices/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/ntheory/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/parsing/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/physics/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/plotting/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/polys/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/printing/pretty/tests/__init__.py' not found
(or not a regular file)
package init file 'sympy/printing/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/series/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/simplify/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/slow_tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/solvers/tests/__init__.py' not found (or not a
regular file)
package init file 'sympy/statistics/tests/__init__.py' not found (or not
a regular file)
package init file 'sympy/test_external/__init__.py' not found (or not a
regular file)
package init file 'sympy/utilities/tests/__init__.py' not found (or not
a regular file)
package init file 'sage/tests/french_book/__init__.py' not found (or not
a regular file)
package init file 'sage/tests/french_book/__init__.py' not found (or not
a regular file)

[Mitesh Patel]

On 09/19/2010 02:53 PM, leif wrote:
> P.S.: I get (grep "regular file" install.log):
>

> [...]

> package init file 'sage/tests/french_book/__init__.py' not found (or not
> a regular file)
> package init file 'sage/tests/french_book/__init__.py' not found (or not
> a regular file)

Thanks for noting this. I've opened

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

for the Sage library messages.

[David Joyner]

Built fine on mac 10.6.5 but the only failure of sage -testall was

sage -t "devel/sage/sage/schemes/generic/toric_divisor.py"

Total time for all tests: 7096.2 seconds
Please see /Users/davidjoyner/.sage//tmp/test.log for the complete log
from this test.
hera:sage-4.6.alpha1 davidjoyner$ ./sage -t
"devel/sage/sage/schemes/generic/toric_divisor.py"
sage -t "devel/sage/sage/schemes/generic/toric_divisor.py"
**********************************************************************
File "/Volumes/Bay2/sagefiles2/sage-4.6.alpha1/devel/sage/sage/schemes/generic/toric_divisor.py",
line 1522:
sage: supp.Vrepresentation()
Expected:
[A vertex at (-1, 1), A vertex at (0, 2), A vertex at (0, -1), A
vertex at (3, -1)]
Got:
[A vertex at (-1, 1), A vertex at (0, 2), A vertex at (3, -1), A
vertex at (0, -1)]
**********************************************************************
1 items had failures:
1 of 10 in __main__.example_35
***Test Failed*** 1 failures.
For whitespace errors, see the file
/Users/davidjoyner/.sage//tmp/.doctest_toric_divisor.py
[29.7 s]

----------------------------------------------------------------------
The following tests failed:

sage -t "devel/sage/sage/schemes/generic/toric_divisor.py"

> #9733: Alexander Dreyer, François Bissey: Parallel build of Singular

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

This is the known #9926.

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

-Leif

> On Sun, Sep 19, 2010 at 2:29 AM, Mitesh Patel <qed...@gmail.com> wrote:

>> [...]

>> == Known problems ==
>>
>> * The long doctests pass for me on redhawk, sage, and t2.math. See
>> #9926 for a failure on bsd.math (32-bit build, OS X 10.6).

>> [...]

[Marshall Hampton]

All tests passed for me on a i7 860 running ubuntu 9.10.

As for #9926, I am still trying to come up with a clean resolution.
Maybe someone else will beat me to it. The cheap and easy hack is
just to sort the output for that doctest. A more systematic solution
is complicated by not wanting to mess with the cddlib output, which
apparently is hardware-dependent.

-Marshall Hampton

[Georg Grafendorfer]

Fedora 13, AMD Phenom II X 4,

built OK,
ptestlong: just one failure, the obligatory one related to

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

Georg

[kcrisman]

I still am getting the known

Exiting Sage (CPU time 0m0.74s, Wall time 11m11.95s).
Exiting spawned GP/PARI interpreter process.

It's not exactly a bug, but it's also annoying and potentially
confusing to a non-Pari user. Is there a ticket for this/not a plan
for a ticket? I feel like this was answered earlier but know I'll
never be able to find it with Google groups search...

- kcrisman

[Mitesh Patel]

Could you open a ticket?

I think the earlier post is from the "New PARI needs testing" thread:

http://groups.google.com/group/sage-devel/browse_thread/thread/94a856f696742038/ede926c1527c19f0#ede926c1527c19f0

[Dima Pasechnik]

With the previous versions of Sage, I often got
"Exiting spawned GAP process" at the exit.

[Dima Pasechnik]

Builds and tests OK on Linux amd64 (Debian unstable). Got one test
failure:

sage -t "devel/sage/sage/interfaces/r.py"
**********************************************************************
File "/usr/local/src/sage/sage-4.6.alpha1/devel/sage/sage/interfaces/
r.py", line 1128:
sage: tmpdir in sageobj(r.getwd())
Expected:
True
Got:
False

that however would not repeat if I tested again...

Dima

On Sep 19, 2:29 pm, Mitesh Patel <qed...@gmail.com> wrote:
> Hi,
>
> We've unleashed Sage 4.6.alpha1.
>
> Source archive:
>

> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6...
>
> Upgrade path:
>
> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6...

>
> Please build, test, and report!  We'd love to hear about your
> experiences with this release.
>
> == Known problems ==
>
>  * The long doctests pass for me on redhawk, sage, and t2.math.  See
> #9926 for a failure on bsd.math (32-bit build, OS X 10.6).
>
>  * The tests also pass on the Skynet cluster, except for cleo and iras
> (both Itanium), where PARI fails to build.  This is #9897.
>
>  * Builds with 'export SAGE_PARALLEL_SPKG_BUILD=yes' could fail with the
> Singular package.  This is #9946.
>
> The full list of blockers is at
>

> http://trac.sagemath.org/sage_trac/query?priority=blocker&group=statu...

> #9733: Alexander Dreyer, Fran�ois Bissey: Parallel build of Singular

[kcrisman]

> Exiting Sage (CPU time 0m0.74s, Wall time 11m11.95s).
> Exiting spawned GP/PARI interpreter process.
> It's not exactly a bug, but it's also annoying and potentially
> confusing to a non-Pari user. Is there a ticket for this/not a plan
> for a ticket? I feel like this was answered earlier but know I'll
> never be able to find it with Google groups search...

> Could you open a ticket?

Sure, it's http://trac.sagemath.org/sage_trac/ticket/9959 . I didn't
make it a blocker, but only because I tend to set priority quite a bit
lower than everyone else :)

On Sep 20, 8:43 pm, Dima Pasechnik <dimp...@gmail.com> wrote:
> With the previous versions of Sage, I often got
> "Exiting spawned GAP process" at the exit.

That is different; every time one moves Sage into a different
directory, GAP has to start up for some reason to make sure it knows
where it is. This should only happen the first time you start a given
Sage build in a given location, and I don't think there is any way
around it.

- kcrisman

[Dima Pasechnik]

Builds and tests OK on PPC MacOSX 10.5, with gcc42 (but no gfortran),
after
applying http://trac.sagemath.org/sage_trac/ticket/9798 (this fixes
one cdd-related test,
that fails on an unpatched system due to a hardware-dependency of a
rng)

Will now trt with gcc+gfortran...

PS. Hi Karl-Dieter, did you manage to try gfortran on 10.4?

On Sep 19, 2:29 pm, Mitesh Patel <qed...@gmail.com> wrote:

> Hi,
>
> We've unleashed Sage 4.6.alpha1.
>
> Source archive:
>

> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6...
>
> Upgrade path:
>
> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6...
>

> Please build, test, and report!  We'd love to hear about your
> experiences with this release.
>
> == Known problems ==
>
>  * The long doctests pass for me on redhawk, sage, and t2.math.  See
> #9926 for a failure on bsd.math (32-bit build, OS X 10.6).
>
>  * The tests also pass on the Skynet cluster, except for cleo and iras
> (both Itanium), where PARI fails to build.  This is #9897.
>
>  * Builds with 'export SAGE_PARALLEL_SPKG_BUILD=yes' could fail with the
> Singular package.  This is #9946.
>
> The full list of blockers is at
>

> http://trac.sagemath.org/sage_trac/query?priority=blocker&group=statu...

> #9733: Alexander Dreyer, Fran�ois Bissey: Parallel build of Singular

[Justin C. Walker]

On Sep 18, 2010, at 23:29 , Mitesh Patel wrote:

> Hi,
>
> We've unleashed Sage 4.6.alpha1.
>
> Source archive:
>
> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1.tar
>
> Upgrade path:
>
> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1/

Built as an upgrade to 4.6.a0 on Mac OS X, 10.6.4 (both Dual Quad Xeon and Core i7). No problems with the upgrade, but tests failed on each system:

Core i7:
sage -t -long "devel/sage/sage/schemes/generic/toric_divisor.py" # 1 doctests failed

Dual Quad Xeon:
sage -t -long devel/sage/sage/plot/plot3d/base.pyx # 4 doctests failed
sage -t -long devel/sage/sage/schemes/generic/toric_divisor.py # 1 doctests failed

Tests were run with
SAGE_PARALLEL_SPKG_BUILD=yes SAGE64=yes MAKE="make -j{3,6}" make ptestlongsage
('3' on Core i7).

Am I right that the "MAKE=" define has no effect?

Logs for the curious are in
sage.math.washington.edu:~justin/logs/{Xeon,i7}-4.6.a1.log

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
Like the ski resort full of girls hunting for husbands
and husbands hunting for girls, the situation is not
as symmetrical as it might seem.
- Alan MacKay
--

[leif]

Justin C. Walker wrote:
> On Sep 18, 2010, at 23:29 , Mitesh Patel wrote:
>
>> Upgrade path:
>>
>> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1/
>
> Built as an upgrade to 4.6.a0 on Mac OS X, 10.6.4 (both Dual Quad Xeon and Core i7). No problems with the upgrade, but tests failed on each system:
>
> Core i7:
> sage -t -long "devel/sage/sage/schemes/generic/toric_divisor.py" # 1 doctests failed
>
> Dual Quad Xeon:
> sage -t -long devel/sage/sage/plot/plot3d/base.pyx # 4 doctests failed
> sage -t -long devel/sage/sage/schemes/generic/toric_divisor.py # 1 doctests failed
>
> Tests were run with
> SAGE_PARALLEL_SPKG_BUILD=yes SAGE64=yes MAKE="make -j{3,6}" make ptestlongsage
> ('3' on Core i7).
>
> Am I right that the "MAKE=" define has no effect?

Perhaps a typo in SAGE_PARALLEL_SPKG_BUILD? (If this is not set to
"yes", MAKE will be reset to "make".)

>
> Logs for the curious are in
> sage.math.washington.edu:~justin/logs/{Xeon,i7}-4.6.a1.log

I *was* curious, unfortunately only test logs... ;-)

-Leif

[Justin C. Walker]

On Sep 21, 2010, at 22:10 , leif wrote:

> Justin C. Walker wrote:
>> On Sep 18, 2010, at 23:29 , Mitesh Patel wrote:
>>
>>> Upgrade path:
>>>
>>> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1/
>>
>> Built as an upgrade to 4.6.a0 on Mac OS X, 10.6.4 (both Dual Quad Xeon and Core i7). No problems with the upgrade, but tests failed on each system:
>>
>> Core i7:
>> sage -t -long "devel/sage/sage/schemes/generic/toric_divisor.py" # 1 doctests failed
>>
>> Dual Quad Xeon:
>> sage -t -long devel/sage/sage/plot/plot3d/base.pyx # 4 doctests failed
>> sage -t -long devel/sage/sage/schemes/generic/toric_divisor.py # 1 doctests failed
>>
>> Tests were run with
>> SAGE_PARALLEL_SPKG_BUILD=yes SAGE64=yes MAKE="make -j{3,6}" make ptestlongsage
>> ('3' on Core i7).
>>
>> Am I right that the "MAKE=" define has no effect?
>
> Perhaps a typo in SAGE_PARALLEL_SPKG_BUILD? (If this is not set to
> "yes", MAKE will be reset to "make".)

Not sure I follow (the above is a copy/paste of the command I used in Terminal)...

>> Logs for the curious are in
>> sage.math.washington.edu:~justin/logs/{Xeon,i7}-4.6.a1.log
>
> I *was* curious, unfortunately only test logs... ;-)

Didja want the whole shebang? I can add install logs to the ptestlog files if it will keep your cat alive...

[leif]

Justin C. Walker wrote:
>
> On Sep 21, 2010, at 22:10 , leif wrote:
>
>> Justin C. Walker wrote:
>>> On Sep 18, 2010, at 23:29 , Mitesh Patel wrote:
>>>
>>>> Upgrade path:
>>>>
>>>> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1/
>>>
>>> Built as an upgrade to 4.6.a0 on Mac OS X, 10.6.4 (both Dual Quad Xeon and Core i7). No problems with the upgrade, but tests failed on each system:
>>>
>>> Core i7:
>>> sage -t -long "devel/sage/sage/schemes/generic/toric_divisor.py" # 1 doctests failed
>>>
>>> Dual Quad Xeon:
>>> sage -t -long devel/sage/sage/plot/plot3d/base.pyx # 4 doctests failed
>>> sage -t -long devel/sage/sage/schemes/generic/toric_divisor.py # 1 doctests failed
>>>
>>> Tests were run with
>>> SAGE_PARALLEL_SPKG_BUILD=yes SAGE64=yes MAKE="make -j{3,6}" make ptestlongsage
>>> ('3' on Core i7).
>>>
>>> Am I right that the "MAKE=" define has no effect?
>>
>> Perhaps a typo in SAGE_PARALLEL_SPKG_BUILD? (If this is not set to
>> "yes", MAKE will be reset to "make".)
>
> Not sure I follow (the above is a copy/paste of the command I used in Terminal)...

Ah, I see. You should have set MAKE before running ./sage -upgrade; the
setting of MAKE has no effect on ptestlong itself. (The number of files
doctested in parallel is max(8, #hardware_threads) unless you edit the
makefile.)

>>> Logs for the curious are in
>>> sage.math.washington.edu:~justin/logs/{Xeon,i7}-4.6.a1.log
>>
>> I *was* curious, unfortunately only test logs... ;-)
>
> Didja want the whole shebang? I can add install logs to the ptestlog files if it will keep your cat alive...

It already got killed by curiosity ��[]_

-Leif

[Justin C. Walker]

On Sep 21, 2010, at 23:16 , leif wrote:
> Justin C. Walker wrote:

[snip]

>>>>
>>>> Tests were run with
>>>> SAGE_PARALLEL_SPKG_BUILD=yes SAGE64=yes MAKE="make -j{3,6}" make ptestlongsage
>>>> ('3' on Core i7).
>>>>
>>>> Am I right that the "MAKE=" define has no effect?
>>>
>>> Perhaps a typo in SAGE_PARALLEL_SPKG_BUILD? (If this is not set to
>>> "yes", MAKE will be reset to "make".)
>>
>> Not sure I follow (the above is a copy/paste of the command I used in Terminal)...
>
> Ah, I see. You should have set MAKE before running ./sage -upgrade; the
> setting of MAKE has no effect on ptestlong itself. (The number of files
> doctested in parallel is max(8, #hardware_threads) unless you edit the
> makefile.)

I seem to recall rumors of that circulating earlier...I should pay more attention to these things, and avoid reinventing the mistake.

>>>> Logs for the curious are in
>>>> sage.math.washington.edu:~justin/logs/{Xeon,i7}-4.6.a1.log
>>>
>>> I *was* curious, unfortunately only test logs... ;-)
>>
>> Didja want the whole shebang? I can add install logs to the ptestlog files if it will keep your cat alive...
>

> It already got killed by curiosity 같[]_

Alas, poor cat...I think I'll let sleeping dogs lie, here...

Thanks!

Justin

--
Justin C. Walker, Curmudgeon at Large

Director
Institute for the Enhancement of the Director's Income
-----------
Nobody knows the trouble I've been
-----------

[kcrisman]

On Sep 22, 12:49 am, "Justin C. Walker" <jus...@mac.com> wrote:
> On Sep 18, 2010, at 23:29 , Mitesh Patel wrote:
>
> > Hi,
>
> > We've unleashed Sage 4.6.alpha1.
>
> > Source archive:
>

> >http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6...
>
> > Upgrade path:
>
> >http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6...
>

> Built as an upgrade to 4.6.a0 on Mac OS X, 10.6.4 (both Dual Quad Xeon and Core i7).  No problems with the upgrade, but tests failed on each system:
>
> Core i7:
>     sage -t -long "devel/sage/sage/schemes/generic/toric_divisor.py" # 1 doctests failed
>
> Dual Quad Xeon:
>         sage -t  -long devel/sage/sage/plot/plot3d/base.pyx # 4 doctests failed
>         sage -t  -long devel/sage/sage/schemes/generic/toric_divisor.py # 1 doctests failed

Great, these are both known bugs. The base.pyx one has to do with PIL
and whether it finds libpng or something like that - it's easy to find
this ticket on Trac. Sadly, no real solution yet that wouldn't have
to do with optional spkgs :(

- kcrisman

[Mitesh Patel]

On 09/20/2010 07:48 PM, Dima Pasechnik wrote:
> Builds and tests OK on Linux amd64 (Debian unstable). Got one test
> failure:
>
> sage -t "devel/sage/sage/interfaces/r.py"
> **********************************************************************
> File "/usr/local/src/sage/sage-4.6.alpha1/devel/sage/sage/interfaces/
> r.py", line 1128:
> sage: tmpdir in sageobj(r.getwd())
> Expected:
> True
> Got:
> False
>
> that however would not repeat if I tested again...

I've opened

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

for this flaky / flakey doctest.

[Dan Drake]

On Sun, 19 Sep 2010 at 01:29AM -0500, Mitesh Patel wrote:
> We've unleashed Sage 4.6.alpha1.
>
> Source archive:
>
> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1.tar
>
> Upgrade path:
>
> http://sage.math.washington.edu/home/release/sage-4.6.alpha1/sage-4.6.alpha1/
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.

Built and passed "ptestlong" tests on a 32-bit Ubuntu Dapper virtual
machine. This is Ubuntu 6.06 and has gcc version 4.0.3. It even passed
the free_module.py test (#9865) which has been problematic for me in
virtual machines with moderate amounts of memory. (This VM has 1GB RAM.)

Dan

--
--- Dan Drake
----- http://mathsci.kaist.ac.kr/~drake
-------