[sage-devel] Re: sage-3.2
Hi Michael, On Tue, Nov 25, 2008 at 6:53 AM, mabshoff [EMAIL PROTECTED] wrote: On Nov 24, 1:48 am, Minh Nguyen [EMAIL PROTECTED] wrote: Hi Michael, Hi Minh, SNIP I re-ran the tests under the above Mac OS X system, using this command: /path-to-sage-root/sage -testall -verbose This time, I only have one failed test, namely sage -t -verbose devel/sage/sage/modular/abvar/homspace.py Yes, but that test took [425.0 s] instead of about 2,000 seconds from your last run - so something strange is going on. Can you rerun that test only a couple times to see if it varies? I've re-ran the test 3 times with the same command as above. In all cases, the results look similar: timed out errors in this test: sage -t -verbose devel/sage/sage/modular/abvar/homspace.py I've uploaded compressed test logs to my web site: http://nguyenminh2.googlepages.com/test-mac-2.log.bz2 http://nguyenminh2.googlepages.com/test-mac-3.log.bz2 http://nguyenminh2.googlepages.com/test-mac-4.log.bz2 But note that the compressed logs are still rather big, about 1.2 MB each. Going back to the case where I had two timed out errors after compiling and testing sage-3.2 for the first time. I think the said two timed out errors might in some weird way be linked to my Energy Saver settings in the System Preferences. During the first test (after which I received 2 timed out errors), my Energy Saver settings were something like putting the computer to sleep when inactive for 15 minutes, and I checked the box for putting the hard disk to sleep whenever possible. But before I re-ran the test as you originally suggested, I changed my Energy Saver settings to never putting the computer to sleep, and I unchecked the box for putting the hard disk to sleep. I had these same settings when I was re-running the test for the next 3 times, links to the logs of which are per this email. 3.2.1.alpha1 will have a fix that shut cut the time of that doctest down by 35% or so. Craig and William also mentioned in IRC that with a little work that homspace code ought to be be cut down to next to nothing since our implementation is allegedly pretty naive. Since Craig did speed up the Victor Miller basis code by a factor of 900 recently I am sure it will happen :) which I think is a timed out error. Total time for all tests: 10643.1 seconds. The test log is huge: about 14 MB uncompressed, and 1.2 MB compressed using bzip2. The relevant section is rather lengthy, so I don't want to post it here. I've uploaded the compressed test log to my web site. If you're interested, here's the link: Ok, good call. All I wanted was the verbose output from the two timed out tests, so the whole thing took a while longer to poke around. -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
Hm, I did a sage -upgrade on Mac OS X 10.4.11 on a MacBook Pro and
everything worked fine. When I start sage, it tells me that it is
Sage Version 3.2, Release Date: 2008-11-20, but when I open a
notebook and type version(), it returns: 'SAGE Version 3.1.4, Release
Date: 2008-10-20'. Both the command line and the notebook give an
error if I want to use pynac by adding ns=1 to a var() command:
--
| Sage Version 3.2, Release Date: 2008-11-20 |
| Type notebook() for the GUI, and license() for information.|
--
sage: var('a b',ns=1)
---
TypeError Traceback (most recent call
last)
/Users/sschym/ipython console in module()
TypeError: var() takes no keyword arguments
Does anyone have an idea what is going on?
Cheers
Stan
On Nov 21, 9:27 pm, Justin C. Walker [EMAIL PROTECTED] wrote:
On Nov 20, 2008, at 1:44 PM, William Stein wrote:
Hi,
For early adopters, sage-3.2 has been released. You can get the
source from here:http://sagemath.org/src/
Or you can do sage -upgrade.
Binaries and an official announcement should come within a day or two.
Mac OS X, 10.5.5 (Dual Quad Xeon):
- installed and built sage-3.2.rc2 w/o problems.
- all tests passed!
Then I upgraded (sage -upgrade) to 3.2 w/o problems, and moved the
install tree to a different volume and did make test with -j6.
All tests passed!
Great work!
Justin
--
Justin C. Walker, Curmudgeon-at-Large
() The ASCII Ribbon Campaign
/\ Help Cure HTML Email
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Sun, Nov 23, 2008 at 12:53 PM, Stan Schymanski [EMAIL PROTECTED] wrote:
Hm, I did a sage -upgrade on Mac OS X 10.4.11 on a MacBook Pro and
everything worked fine. When I start sage, it tells me that it is
Sage Version 3.2, Release Date: 2008-11-20, but when I open a
notebook and type version(), it returns: 'SAGE Version 3.1.4, Release
Date: 2008-10-20'. Both the command line and the notebook give an
error if I want to use pynac by adding ns=1 to a var() command:
--
| Sage Version 3.2, Release Date: 2008-11-20 |
| Type notebook() for the GUI, and license() for information.|
--
sage: var('a b',ns=1)
---
TypeError Traceback (most recent call
last)
/Users/sschym/ipython console in module()
TypeError: var() takes no keyword arguments
Does anyone have an idea what is going on?
Cheers
The upgrade failed somehow. Try this:
sage: hg_sage.pull()
sage: hg_sage.merge()
sage: quit
sage -br
and see if things are any better.
William
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
Hi William, Thanks a lot for that, it works now. The last command took a long time (an hour or so). Stan William Stein wrote: The upgrade failed somehow. Try this: sage: hg_sage.pull() sage: hg_sage.merge() sage: quit sage -br and see if things are any better. William --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
I just built 3.2 on this 64-bit linux machine: Linux version 2.6.18.8-0.3-default ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Tue Apr 17 08:42:35 UTC 2007 Testing gives this error: [EMAIL PROTECTED]/sage -t devel/sage/sage/calculus/equations.py sage -t devel/sage/sage/calculus/equations.py Unhandled SIGSEGV: A segmentation fault occured in SAGE. This probably occured because a *compiled* component of SAGE has a bug in it (typically accessing invalid memory) or is not properly wrapped with _sig_on, _sig_off. You might want to run SAGE under gdb with 'sage -gdb' to debug this. SAGE will now terminate (sorry). A mysterious error (perphaps a memory error?) occurred, which may have crashed doctest. [3.9 s] exit code: 768 -- The following tests failed: sage -t devel/sage/sage/calculus/equations.py Total time for all tests: 3.9 seconds I ran it again with -verbose and that time it passed. John On 21 Nov, 20:46, mabshoff [EMAIL PROTECTED] wrote: On Nov 21, 12:42 pm, Octoploid [EMAIL PROTECTED] wrote: On Nov 21, 7:51 pm, mabshoff [EMAIL PROTECTED] wrote: SNIP This seems to indicate that you upgraded from a binary build with a C+ + compiler using a different ABI. What did you upgrade from? Did you upgrade the C++ compiler since you last time build Sage? There was an old and unused version of /usr/lib/libstdc++.so on my system. Libpynac must somehow picked it up. I removed the library and rebuild sage. Now everything runs fine. Ok, that sounds about right :) BTW is there a way to pass -j3 to sage -upgrade ? export MAKE=make -j3 and then run sage -upgrade Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
William Stein wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here: http://sagemath.org/src/ Or you can do sage -upgrade. Binaries and an official announcement should come within a day or two. William After sage -upgrade I get: [EMAIL PROTECTED] sage-3.2]$ sage -- | Sage Version 3.2, Release Date: 2008-11-20 | | Type notebook() for the GUI, and license() for information.| -- Traceback (most recent call last): File /usr/local/sage/local/bin/sage-location, line 134, in module t, R = install_moved() File /usr/local/sage/local/bin/sage-location, line 18, in install_moved write_flags_file() File /usr/local/sage/local/bin/sage-location, line 63, in write_flags_file open(flags_file,'w').write(get_flags_info()) IOError: [Errno 13] Permission denied: '/usr/local/sage/local/lib/sage-flags.txt' Thoughts? Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
Jaap Spies wrote: William Stein wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here: http://sagemath.org/src/ Or you can do sage -upgrade. Binaries and an official announcement should come within a day or two. William After sage -upgrade I get: [EMAIL PROTECTED] sage-3.2]$ sage -- | Sage Version 3.2, Release Date: 2008-11-20 | | Type notebook() for the GUI, and license() for information.| -- Traceback (most recent call last): File /usr/local/sage/local/bin/sage-location, line 134, in module t, R = install_moved() File /usr/local/sage/local/bin/sage-location, line 18, in install_moved write_flags_file() File /usr/local/sage/local/bin/sage-location, line 63, in write_flags_file open(flags_file,'w').write(get_flags_info()) IOError: [Errno 13] Permission denied: '/usr/local/sage/local/lib/sage-flags.txt' Thoughts? Jaap Sorry for the noise: As root: chmod a+rX -R /usr/local/sage solved the (non) issue. Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 22, 2:06 pm, Jaap Spies [EMAIL PROTECTED] wrote: Jaap Spies wrote: William Stein wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. Binaries and an official announcement should come within a day or two. William After sage -upgrade I get: [EMAIL PROTECTED] sage-3.2]$ sage -- | Sage Version 3.2, Release Date: 2008-11-20 | | Type notebook() for the GUI, and license() for information. | -- Traceback (most recent call last): File /usr/local/sage/local/bin/sage-location, line 134, in module t, R = install_moved() File /usr/local/sage/local/bin/sage-location, line 18, in install_moved write_flags_file() File /usr/local/sage/local/bin/sage-location, line 63, in write_flags_file open(flags_file,'w').write(get_flags_info()) IOError: [Errno 13] Permission denied: '/usr/local/sage/local/lib/sage-flags.txt' Thoughts? Jaap Sorry for the noise: As root: chmod a+rX -R /usr/local/sage solved the (non) issue. I am not so sure this is a non-issue since that file should be created with the right permissions. Let me think about it before I come to any conclusion. Meanwhile: Did you upgrade as root? Who owned the tree before? Jaap Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
Hi Jaap, On 22 Nov., 22:54, Jaap Spies [EMAIL PROTECTED] wrote: William Stein wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. Binaries and an official announcement should come within a day or two. William After sage -upgrade I get: [EMAIL PROTECTED] sage-3.2]$ sage -- | Sage Version 3.2, Release Date: 2008-11-20 | | Type notebook() for the GUI, and license() for information. | -- Traceback (most recent call last): File /usr/local/sage/local/bin/sage-location, line 134, in module t, R = install_moved() File /usr/local/sage/local/bin/sage-location, line 18, in install_moved write_flags_file() File /usr/local/sage/local/bin/sage-location, line 63, in write_flags_file open(flags_file,'w').write(get_flags_info()) IOError: [Errno 13] Permission denied: '/usr/local/sage/local/lib/sage-flags.txt' Thoughts? Jaap that file sage-flags.txt came in due to a recent patch I was the reviewer for. The intention is to store on Linux systems, with which processor flags a binary distribution was originally compiled, in order to catch certain hard-to-debug failures. Obviously, there is some reason for the existence of a trac ticket saying rename 'sage -upgrade' to 'sage -expert-upgrade' , because in between releases certain things might break. (We did test fresh installations ...) Now if you don't have a Linux system (but say e.g. a Mac), just create an empty sage-flags.txt file there and everything will be fine. If that does not work for you, the probably easiest thing (taking only some time) for you is to download a Sage 3.2 source tarball, install that one somewhere temporarily, and copy at least the then created file %TMP_SAGE_ROOT/local/lib/sage-flags.txt over. Of course it would be best to know why on earth the sage-location script suddenly does not seem to have the rights to create a new file in your /usr/local/sage/local/ directory ... but I have no clue. Cheers, gsw --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Sat, Nov 22, 2008 at 2:09 PM, mabshoff [EMAIL PROTECTED] wrote: On Nov 22, 2:06 pm, Jaap Spies [EMAIL PROTECTED] wrote: Jaap Spies wrote: William Stein wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. Binaries and an official announcement should come within a day or two. William After sage -upgrade I get: [EMAIL PROTECTED] sage-3.2]$ sage -- | Sage Version 3.2, Release Date: 2008-11-20 | | Type notebook() for the GUI, and license() for information.| -- Traceback (most recent call last): File /usr/local/sage/local/bin/sage-location, line 134, in module t, R = install_moved() File /usr/local/sage/local/bin/sage-location, line 18, in install_moved write_flags_file() File /usr/local/sage/local/bin/sage-location, line 63, in write_flags_file open(flags_file,'w').write(get_flags_info()) IOError: [Errno 13] Permission denied: '/usr/local/sage/local/lib/sage-flags.txt' Thoughts? Jaap Sorry for the noise: As root: chmod a+rX -R /usr/local/sage solved the (non) issue. I am not so sure this is a non-issue since that file should be created with the right permissions. Let me think about it before I come to any conclusion. Meanwhile: Did you upgrade as root? Who owned the tree before? I'm guessing no test run of Sage occurred as the user (root) doing the upgrade. I think sage -upgrade should always run that sage-starts script I recently wrote at least once, say at the end. That will make sure that sage-location gets updated, etc. Thoughts? William Jaap Cheers, Michael -- 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Sat, Nov 22, 2008 at 2:22 PM, Georg S. Weber [EMAIL PROTECTED] wrote: Hi Jaap, On 22 Nov., 22:54, Jaap Spies [EMAIL PROTECTED] wrote: William Stein wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. Binaries and an official announcement should come within a day or two. William After sage -upgrade I get: [EMAIL PROTECTED] sage-3.2]$ sage -- | Sage Version 3.2, Release Date: 2008-11-20 | | Type notebook() for the GUI, and license() for information.| -- Traceback (most recent call last): File /usr/local/sage/local/bin/sage-location, line 134, in module t, R = install_moved() File /usr/local/sage/local/bin/sage-location, line 18, in install_moved write_flags_file() File /usr/local/sage/local/bin/sage-location, line 63, in write_flags_file open(flags_file,'w').write(get_flags_info()) IOError: [Errno 13] Permission denied: '/usr/local/sage/local/lib/sage-flags.txt' Thoughts? Jaap that file sage-flags.txt came in due to a recent patch I was the reviewer for. The intention is to store on Linux systems, with which processor flags a binary distribution was originally compiled, in order to catch certain hard-to-debug failures. Obviously, there is some reason for the existence of a trac ticket saying rename 'sage -upgrade' to 'sage -expert-upgrade' , because in between releases certain things might break. (We did test fresh installations ...) Now if you don't have a Linux system (but say e.g. a Mac), just create an empty sage-flags.txt file there and everything will be fine. If that does not work for you, the probably easiest thing (taking only some time) for you is to download a Sage 3.2 source tarball, install that one somewhere temporarily, and copy at least the then created file %TMP_SAGE_ROOT/local/lib/sage-flags.txt over. Of course it would be best to know why on earth the sage-location script suddenly does not seem to have the rights to create a new file in your /usr/local/sage/local/ directory ... but I have no clue. It's undoubtedly because the user did sage -upgrade as root, but didn't run Sage ever as root. The right solution is for the user to just type sage once as root. -- William --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
mabshoff wrote: On Nov 22, 2:06 pm, Jaap Spies [EMAIL PROTECTED] wrote: Jaap Spies wrote: William Stein wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. Binaries and an official announcement should come within a day or two. William After sage -upgrade I get: [EMAIL PROTECTED] sage-3.2]$ sage -- | Sage Version 3.2, Release Date: 2008-11-20 | | Type notebook() for the GUI, and license() for information.| -- Traceback (most recent call last): File /usr/local/sage/local/bin/sage-location, line 134, in module t, R = install_moved() File /usr/local/sage/local/bin/sage-location, line 18, in install_moved write_flags_file() File /usr/local/sage/local/bin/sage-location, line 63, in write_flags_file open(flags_file,'w').write(get_flags_info()) IOError: [Errno 13] Permission denied: '/usr/local/sage/local/lib/sage-flags.txt' Thoughts? Jaap Sorry for the noise: As root: chmod a+rX -R /usr/local/sage solved the (non) issue. I am not so sure this is a non-issue since that file should be created with the right permissions. Let me think about it before I come to any conclusion. Meanwhile: Did you upgrade as root? Who owned the tree before? I have a system wide sage install owned by root in /usr/local/sage. I always upgrade the install as root. And most of the time I think of doing the chmod. See the rich history of this install! [EMAIL PROTECTED] installed]# ls sage-* sage-1.5.1.2 sage-1.8.2.1 sage-2.10.3 sage-2.4 sage-2.5.3 sage-2.8.13 sage-2.8.4.1 sage-2.8.9sage-3.0.5 sage-1.5.3sage-1.9 sage-2.10.4 sage-2.4.1sage-2.6 sage-2.8.14 sage-2.8.4.2 sage-2.9 sage-3.0.6 sage-1.6 sage-2.0 sage-2.11 sage-2.4.1.2 sage-2.7 sage-2.8.15 sage-2.8.5sage-2.9.1.1 sage-3.1 sage-1.6.1sage-2.1 sage-2.1.3sage-2.4.2sage-2.7.3 sage-2.8.2sage-2.8.5.1 sage-2.9.2sage-3.1.1 sage-1.7 sage-2.10 sage-2.1.3.1 sage-2.5 sage-2.8 sage-2.8.3sage-2.8.6sage-3.0 sage-3.1.2 sage-1.7.1sage-2.1.0.1 sage-2.1.4sage-2.5.0.2 sage-2.8.10 sage-2.8.3.3 sage-2.8.7sage-3.0.2sage-3.1.4 sage-1.8 sage-2.10.1 sage-2.2 sage-2.5.1sage-2.8.11 sage-2.8.3.6 sage-2.8.8sage-3.0.3sage-3.2 sage-1.8.1sage-2.10.2 sage-2.3 sage-2.5.2sage-2.8.12 sage-2.8.4sage-2.8.8.1 sage-3.0.4 [EMAIL PROTECTED] installed]# Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
See the rich history of this install! [EMAIL PROTECTED] installed]# ls sage-* sage-1.5.1.2 sage-1.8.2.1 sage-2.10.3 sage-2.4 sage-2.5.3 sage-2.8.13 sage-2.8.4.1 sage-2.8.9 sage-3.0.5 sage-1.5.3 sage-1.9 sage-2.10.4 sage-2.4.1 sage-2.6 sage-2.8.14 sage-2.8.4.2 sage-2.9 sage-3.0.6 sage-1.6 sage-2.0 sage-2.11 sage-2.4.1.2 sage-2.7 sage-2.8.15 sage-2.8.5 sage-2.9.1.1 sage-3.1 sage-1.6.1 sage-2.1 sage-2.1.3 sage-2.4.2 sage-2.7.3 sage-2.8.2 sage-2.8.5.1 sage-2.9.2 sage-3.1.1 sage-1.7 sage-2.10 sage-2.1.3.1 sage-2.5 sage-2.8 sage-2.8.3 sage-2.8.6 sage-3.0 sage-3.1.2 sage-1.7.1 sage-2.1.0.1 sage-2.1.4 sage-2.5.0.2 sage-2.8.10 sage-2.8.3.3 sage-2.8.7 sage-3.0.2 sage-3.1.4 sage-1.8 sage-2.10.1 sage-2.2 sage-2.5.1 sage-2.8.11 sage-2.8.3.6 sage-2.8.8 sage-3.0.3 sage-3.2 sage-1.8.1 sage-2.10.2 sage-2.3 sage-2.5.2 sage-2.8.12 sage-2.8.4 sage-2.8.8.1 sage-3.0.4 [EMAIL PROTECTED] installed]# Jaap Wow!! I started with Sage 2.9.2 in January this year ... Concerning the issue in discussion, I just opened trac ticket #4585 for it. BTW: What is the state of sage -expert-upgrade ticket #3944? It's gotten stale ... Cheers, gsw --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
William Stein wrote: It's undoubtedly because the user did sage -upgrade as root, but didn't run Sage ever as root. The right solution is for the user to just type sage once as root. Shouldn't this be part of the upgrade process? Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Sat, Nov 22, 2008 at 2:47 PM, Georg S. Weber [EMAIL PROTECTED] wrote: See the rich history of this install! [EMAIL PROTECTED] installed]# ls sage-* sage-1.5.1.2 sage-1.8.2.1 sage-2.10.3 sage-2.4 sage-2.5.3 sage-2.8.13 sage-2.8.4.1 sage-2.8.9sage-3.0.5 sage-1.5.3sage-1.9 sage-2.10.4 sage-2.4.1sage-2.6 sage-2.8.14 sage-2.8.4.2 sage-2.9 sage-3.0.6 sage-1.6 sage-2.0 sage-2.11 sage-2.4.1.2 sage-2.7 sage-2.8.15 sage-2.8.5sage-2.9.1.1 sage-3.1 sage-1.6.1sage-2.1 sage-2.1.3sage-2.4.2sage-2.7.3 sage-2.8.2sage-2.8.5.1 sage-2.9.2sage-3.1.1 sage-1.7 sage-2.10 sage-2.1.3.1 sage-2.5 sage-2.8 sage-2.8.3sage-2.8.6sage-3.0 sage-3.1.2 sage-1.7.1sage-2.1.0.1 sage-2.1.4sage-2.5.0.2 sage-2.8.10 sage-2.8.3.3 sage-2.8.7sage-3.0.2sage-3.1.4 sage-1.8 sage-2.10.1 sage-2.2 sage-2.5.1sage-2.8.11 sage-2.8.3.6 sage-2.8.8sage-3.0.3sage-3.2 sage-1.8.1sage-2.10.2 sage-2.3 sage-2.5.2sage-2.8.12 sage-2.8.4sage-2.8.8.1 sage-3.0.4 [EMAIL PROTECTED] installed]# Jaap Wow!! I started with Sage 2.9.2 in January this year ... Concerning the issue in discussion, I just opened trac ticket #4585 for it. BTW: What is the state of sage -expert-upgrade ticket #3944? It's gotten stale ... I'm marking it as invalid. I wrote the patch, and I suggested this, but things have got better and better regarding sage -upgrade, and we should really aim to do things right and have sage -upgrade just work when possible. It might be a very good idea to have sage -upgrade interactively ask the user if they really want to do this if they are upgrading a binary. If a user built from source in the first place, sage -upgrade is pretty likely to work (or at least, should be supported). If they installed a binary, it's reasonable to worry. Alternatively, maybe sage -upgrade should always interactively have a little quiz... :-). -- William --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Sat, Nov 22, 2008 at 2:54 PM, mabshoff [EMAIL PROTECTED] wrote: On Nov 22, 2:24 pm, Jaap Spies [EMAIL PROTECTED] wrote: mabshoff wrote: SNIP I have a system wide sage install owned by root in /usr/local/sage. I always upgrade the install as root. And most of the time I think of doing the chmod. See the rich history of this install! [EMAIL PROTECTED] installed]# ls sage-* sage-1.5.1.2 sage-1.8.2.1 sage-2.10.3 sage-2.4 sage-2.5.3 sage-2.8.13 sage-2.8.4.1 sage-2.8.9sage-3.0.5 sage-1.5.3sage-1.9 sage-2.10.4 sage-2.4.1sage-2.6 sage-2.8.14 sage-2.8.4.2 sage-2.9 sage-3.0.6 sage-1.6 sage-2.0 sage-2.11 sage-2.4.1.2 sage-2.7 sage-2.8.15 sage-2.8.5sage-2.9.1.1 sage-3.1 sage-1.6.1sage-2.1 sage-2.1.3sage-2.4.2sage-2.7.3 sage-2.8.2sage-2.8.5.1 sage-2.9.2sage-3.1.1 sage-1.7 sage-2.10 sage-2.1.3.1 sage-2.5 sage-2.8 sage-2.8.3sage-2.8.6sage-3.0 sage-3.1.2 sage-1.7.1sage-2.1.0.1 sage-2.1.4sage-2.5.0.2 sage-2.8.10 sage-2.8.3.3 sage-2.8.7sage-3.0.2sage-3.1.4 sage-1.8 sage-2.10.1 sage-2.2 sage-2.5.1sage-2.8.11 sage-2.8.3.6 sage-2.8.8sage-3.0.3sage-3.2 sage-1.8.1sage-2.10.2 sage-2.3 sage-2.5.2sage-2.8.12 sage-2.8.4sage-2.8.8.1 sage-3.0.4 [EMAIL PROTECTED] installed]# Wow - *70* Sage upgrades on the same install. I guess this would make it one of the older installs around :) It could very well be the older actively used sage install around. My oldest is the system-wide one on sage.math, which only goes back to sage-2.3 (but Jaap's goes back to sage-1.6!). Mine's been upgraded 64 times: [EMAIL PROTECTED]:~/s/spkg/installed$ ls -1 sage-*|wc -l 64 My spkg/archive directory is pretty big: [EMAIL PROTECTED]:~/s/spkg$ du -sch archive/ 566Marchive/ 566Mtotal All that stuff can be safely deleted. It probably should be deleted by default these days -- it's just where old stuff from spkg/standard (say) goes during upgrades. [EMAIL PROTECTED]:~/s/spkg$ rm -rf archive/* William Shouldn't this be part of the upgrade process? Yes, and Georg opened a ticket for that already. Jaap Cheers, Michael -- 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Sat, Nov 22, 2008 at 3:06 PM, mabshoff [EMAIL PROTECTED] wrote: On Nov 22, 2:57 pm, William Stein [EMAIL PROTECTED] wrote: On Sat, Nov 22, 2008 at 2:54 PM, mabshoff [EMAIL PROTECTED] wrote: On Nov 22, 2:24 pm, Jaap Spies [EMAIL PROTECTED] wrote: mabshoff wrote: SNIP I have a system wide sage install owned by root in /usr/local/sage. I always upgrade the install as root. And most of the time I think of doing the chmod. See the rich history of this install! [EMAIL PROTECTED] installed]# ls sage-* sage-1.5.1.2 sage-1.8.2.1 sage-2.10.3 sage-2.4 sage-2.5.3 sage-2.8.13 sage-2.8.4.1 sage-2.8.9sage-3.0.5 sage-1.5.3sage-1.9 sage-2.10.4 sage-2.4.1sage-2.6 sage-2.8.14 sage-2.8.4.2 sage-2.9 sage-3.0.6 sage-1.6 sage-2.0 sage-2.11 sage-2.4.1.2 sage-2.7 sage-2.8.15 sage-2.8.5sage-2.9.1.1 sage-3.1 sage-1.6.1sage-2.1 sage-2.1.3sage-2.4.2sage-2.7.3 sage-2.8.2sage-2.8.5.1 sage-2.9.2sage-3.1.1 sage-1.7 sage-2.10 sage-2.1.3.1 sage-2.5 sage-2.8 sage-2.8.3sage-2.8.6sage-3.0 sage-3.1.2 sage-1.7.1sage-2.1.0.1 sage-2.1.4sage-2.5.0.2 sage-2.8.10 sage-2.8.3.3 sage-2.8.7sage-3.0.2sage-3.1.4 sage-1.8 sage-2.10.1 sage-2.2 sage-2.5.1sage-2.8.11 sage-2.8.3.6 sage-2.8.8sage-3.0.3sage-3.2 sage-1.8.1sage-2.10.2 sage-2.3 sage-2.5.2sage-2.8.12 sage-2.8.4sage-2.8.8.1 sage-3.0.4 [EMAIL PROTECTED] installed]# Wow - *70* Sage upgrades on the same install. I guess this would make it one of the older installs around :) It could very well be the older actively used sage install around. My oldest is the system-wide one on sage.math, which only goes back to sage-2.3 (but Jaap's goes back to sage-1.6!). Mine's been upgraded 64 times: [EMAIL PROTECTED]:~/s/spkg/installed$ ls -1 sage-*|wc -l 64 Well, technically that is 63 upgrades :) My spkg/archive directory is pretty big: [EMAIL PROTECTED]:~/s/spkg$ du -sch archive/ 566Marchive/ 566Mtotal All that stuff can be safely deleted. It probably should be deleted by default these days -- it's just where old stuff from spkg/standard (say) goes during upgrades. [EMAIL PROTECTED]:~/s/spkg$ rm -rf archive/* Or it should truncate the no longer used spkgs to zero bytes. We already have a ticket to do so, but I can't find it right now. No, it shouldn't do that. It should just delete them. There's no reason to truncate them to 0 bytes. Am I missing something? What did you have in mind? -- William --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
William Stein wrote: My spkg/archive directory is pretty big: [EMAIL PROTECTED]:~/s/spkg$ du -sch archive/ 566Marchive/ 566Mtotal [EMAIL PROTECTED] spkg]# du -sch archive/ 3.6Garchive/ 3.6Gtotal All that stuff can be safely deleted. It probably should be deleted by default these days -- it's just where old stuff from spkg/standard (say) goes during upgrades. Thanks! Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Sat, Nov 22, 2008 at 3:09 PM, Jaap Spies [EMAIL PROTECTED] wrote: William Stein wrote: My spkg/archive directory is pretty big: [EMAIL PROTECTED]:~/s/spkg$ du -sch archive/ 566Marchive/ 566Mtotal [EMAIL PROTECTED] spkg]# du -sch archive/ 3.6Garchive/ 3.6Gtotal All that stuff can be safely deleted. It probably should be deleted by default these days -- it's just where old stuff from spkg/standard (say) goes during upgrades. The only reason that archive/ directory exists is that when I wrote the Sage package system I was very paranoid about never ever deleting anything, for fear of losing valuable work. But it's kind of ridiculous that you're wasting 3.6GB of disk space. Has anybody reading this *ever* looked in spkg/archive/?? If not, I vote for eliminating it entirely, and deleting old spkg's when their being upgraded instead of moving them to spkg/archive. William --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 22, 2008, at 6:11 PM, William Stein wrote: The only reason that archive/ directory exists is that when I wrote the Sage package system I was very paranoid about never ever deleting anything, for fear of losing valuable work. But it's kind of ridiculous that you're wasting 3.6GB of disk space. Has anybody reading this *ever* looked in spkg/archive/?? If not, I vote for eliminating it entirely, and deleting old spkg's when their being upgraded instead of moving them to spkg/archive. William What about making the archive an option on the upgrade in case something goes wrong? I think most people would be fine with eliminating it, but it might be nice to have as an upgrade option. Cheers, Tim. --- Tim Lahey PhD Candidate, Systems Design Engineering University of Waterloo --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 22, 3:08 pm, William Stein [EMAIL PROTECTED] wrote: On Sat, Nov 22, 2008 at 3:06 PM, mabshoff [EMAIL PROTECTED] wrote: SNIP Or it should truncate the no longer used spkgs to zero bytes. We already have a ticket to do so, but I can't find it right now. No, it shouldn't do that. It should just delete them. There's no reason to truncate them to 0 bytes. Am I missing something? What did you have in mind? Bragging rights, i.e My Sage install is older than yours :) - but if people would just want to delete the archived spkgs I would be fine with that. -- William Jaap: Out of curiosity: how large is your install.log by now? Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Sat, Nov 22, 2008 at 3:15 PM, Tim Lahey [EMAIL PROTECTED] wrote: On Nov 22, 2008, at 6:11 PM, William Stein wrote: The only reason that archive/ directory exists is that when I wrote the Sage package system I was very paranoid about never ever deleting anything, for fear of losing valuable work. But it's kind of ridiculous that you're wasting 3.6GB of disk space. Has anybody reading this *ever* looked in spkg/archive/?? If not, I vote for eliminating it entirely, and deleting old spkg's when their being upgraded instead of moving them to spkg/archive. William What about making the archive an option on the upgrade in case something goes wrong? I think most people would be fine with eliminating it, but it might be nice to have as an upgrade option. Sure, if there actually is somebody out there who has ever used the spkg/archive. I'm kind of guessing nobody has ever used it, in which case it seems completely pointless to support. William --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
William Stein wrote: On Sat, Nov 22, 2008 at 3:15 PM, Tim Lahey [EMAIL PROTECTED] wrote: it might be nice to have as an upgrade option. Sure, if there actually is somebody out there who has ever used the spkg/archive. I'm kind of guessing nobody has ever used it, in which case it seems completely pointless to support. I never used it. I even didn't notice it was there taking space! Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: [Bulk] [sage-devel] Re: sage-3.2
It might be a very good idea to have sage -upgrade interactively ask the user if they really want to do this if they are upgrading a binary. If a user built from source in the first place, sage -upgrade is pretty likely to work (or at least, should be supported). If they installed a binary, it's reasonable to worry. Alternatively, maybe sage -upgrade should always interactively have a little quiz... :-). -- William +1 on having a quiz, but I have some reservations about it. When doing upgrades, one thing that I don't like is to have the install stop all the time asking for questions. The problem is that sage compilation takes a lot of time and I like to let it do that in the night. If one stops all the time, I have to be there to answer everything. That already happens with unresolved merges :( The ideal would be if the upgrade process made the 'quiz' in the beginning, so the user could answer everything up front. Ronan Paixão --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 22, 3:41 pm, Ronan Paixão [EMAIL PROTECTED] wrote: It might be a very good idea to have sage -upgrade interactively ask the user if they really want to do this if they are upgrading a binary. If a user built from source in the first place, sage -upgrade is pretty likely to work (or at least, should be supported). If they installed a binary, it's reasonable to worry. Alternatively, maybe sage -upgrade should always interactively have a little quiz... :-). -- William +1 on having a quiz, but I have some reservations about it. When doing upgrades, one thing that I don't like is to have the install stop all the time asking for questions. The problem is that sage compilation takes a lot of time and I like to let it do that in the night. If one stops all the time, I have to be there to answer everything. That already happens with unresolved merges :( The ideal would be if the upgrade process made the 'quiz' in the beginning, so the user could answer everything up front. The suggestion was a joke :) Ronan Paixão Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
Em Sáb, 2008-11-22 às 15:17 -0800, William Stein escreveu: On Sat, Nov 22, 2008 at 3:15 PM, Tim Lahey [EMAIL PROTECTED] wrote: On Nov 22, 2008, at 6:11 PM, William Stein wrote: The only reason that archive/ directory exists is that when I wrote the Sage package system I was very paranoid about never ever deleting anything, for fear of losing valuable work. But it's kind of ridiculous that you're wasting 3.6GB of disk space. Has anybody reading this *ever* looked in spkg/archive/?? If not, I vote for eliminating it entirely, and deleting old spkg's when their being upgraded instead of moving them to spkg/archive. William What about making the archive an option on the upgrade in case something goes wrong? I think most people would be fine with eliminating it, but it might be nice to have as an upgrade option. Sure, if there actually is somebody out there who has ever used the spkg/archive. I'm kind of guessing nobody has ever used it, in which case it seems completely pointless to support. William A compromise option would be to delete all versions except the one that's being upgraded from, so that archive/ only has one version. But even that may be pointless, since having previous versions is the whole point of using a version control system, and sage uses mercurial, which should allow to revert to old spkgs. Ronan Paixão --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 22, 6:43 pm, Ronan Paixão [EMAIL PROTECTED] wrote: SNIP Sure, if there actually is somebody out there who has ever used the spkg/archive. I'm kind of guessing nobody has ever used it, in which case it seems completely pointless to support. William A compromise option would be to delete all versions except the one that's being upgraded from, so that archive/ only has one version. But even that may be pointless, since having previous versions is the whole point of using a version control system, and sage uses mercurial, which should allow to revert to old spkgs. Nope, that won't work. Setting aside a few exceptions none of the code in src in the spkgs is actually checked into the mercurial repos. There is also no convenient way to figure out which spkgs were used by sage release x.z.y. Ronan Paixão Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Thu, Nov 20, 2008 at 1:44 PM, William Stein [EMAIL PROTECTED] wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here: http://sagemath.org/src/ Or you can do sage -upgrade. Sage-3.2 built and passed all tests on these 32-bit x86 systems: -- Fedora 9, Kernel 2.6.25-14.fc9.i686 -- Debian Lenny (testing), Kernel 2.6.26-1-686 The source distro built fine on the following 32-bit system: Machine Model: MacBook2,1 Processor Name: Intel Core 2 Duo Processor Speed: 2 GHz Memory: 1 GB System Version: Mac OS X 10.4.8 (8N1430) Kernel Version: Darwin 8.8.5 All tests passed, except for the following two sage -t devel/sage/sage/combinat/root_system/weyl_characters.py sage -t devel/sage/sage/modular/abvar/homspace.py which gave (harmless) timed out errors. Here are the relevant error messages: sage -t devel/sage/sage/combinat/root_system/weyl_characters.py*** *** Error: TIMED OUT! *** *** *** *** Error: TIMED OUT! *** *** [2420.7 s] sage -t devel/sage/sage/modular/abvar/homspace.py *** *** Error: TIMED OUT! *** *** *** *** Error: TIMED OUT! *** *** [2622.1 s] -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 22, 11:46 pm, Minh Nguyen [EMAIL PROTECTED] wrote: On Thu, Nov 20, 2008 at 1:44 PM, William Stein [EMAIL PROTECTED] wrote: Hi Minh, Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. Sage-3.2 built and passed all tests on these 32-bit x86 systems: -- Fedora 9, Kernel 2.6.25-14.fc9.i686 -- Debian Lenny (testing), Kernel 2.6.26-1-686 Excellent. The source distro built fine on the following 32-bit system: Machine Model: MacBook2,1 Processor Name: Intel Core 2 Duo Processor Speed: 2 GHz Memory: 1 GB System Version: Mac OS X 10.4.8 (8N1430) Kernel Version: Darwin 8.8.5 All tests passed, except for the following two sage -t devel/sage/sage/combinat/root_system/weyl_characters.py sage -t devel/sage/sage/modular/abvar/homspace.py which gave (harmless) timed out errors. Here are the relevant error messages: sage -t devel/sage/sage/combinat/root_system/weyl_characters.py*** *** Error: TIMED OUT! *** *** *** *** Error: TIMED OUT! *** *** [2420.7 s] #4464 sage -t devel/sage/sage/modular/abvar/homspace.py *** *** Error: TIMED OUT! *** *** *** *** Error: TIMED OUT! *** *** [2622.1 s] #4463 In total: ouch - how much RAM does that box have? The only reason the timings could be so long if those tests get pushed deeply into swap. -- Regards Minh Van Nguyen Cheers, Michael Web:http://nguyenminh2.googlepages.com Blog:http://mvngu.wordpress.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Sat, Nov 22, 2008 at 11:49 PM, mabshoff [EMAIL PROTECTED] wrote: [...] The source distro built fine on the following 32-bit system: Machine Model: MacBook2,1 Processor Name: Intel Core 2 Duo Processor Speed: 2 GHz Memory: 1 GB System Version: Mac OS X 10.4.8 (8N1430) Kernel Version: Darwin 8.8.5 All tests passed, except for the following two sage -t devel/sage/sage/combinat/root_system/weyl_characters.py sage -t devel/sage/sage/modular/abvar/homspace.py which gave (harmless) timed out errors. Here are the relevant error messages: sage -t devel/sage/sage/combinat/root_system/weyl_characters.py*** *** Error: TIMED OUT! *** *** *** *** Error: TIMED OUT! *** *** [2420.7 s] #4464 sage -t devel/sage/sage/modular/abvar/homspace.py *** *** Error: TIMED OUT! *** *** *** *** Error: TIMED OUT! *** *** [2622.1 s] #4463 In total: ouch - how much RAM does that box have? The only reason the timings could be so long if those tests get pushed deeply into swap. 1.0 GB of RAM -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 22, 11:54 pm, Minh Nguyen [EMAIL PROTECTED] wrote: On Sat, Nov 22, 2008 at 11:49 PM, mabshoff [EMAIL PROTECTED] wrote: [...] The source distro built fine on the following 32-bit system: Machine Model: MacBook2,1 Processor Name: Intel Core 2 Duo Processor Speed: 2 GHz Memory: 1 GB System Version: Mac OS X 10.4.8 (8N1430) Kernel Version: Darwin 8.8.5 SNIP Hi Min, In total: ouch - how much RAM does that box have? The only reason the timings could be so long if those tests get pushed deeply into swap. 1.0 GB of RAM Yeah, once I hit send I noticed that you did list the amount of RAM for that box. That is extremely strange that those tests take about 20 times as long as I would expect. Can you rerun them to see if the problem is reproducible? You can also run with -verbose and hopefully something will jump out. -- Regards Minh Van Nguyen Cheers, Michael Web:http://nguyenminh2.googlepages.com Blog:http://mvngu.wordpress.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 20, 10:44 pm, William Stein [EMAIL PROTECTED] wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. I ran sage -upgrade on my system amd64, gcc 4.3.2. This is what I get after upgrading: sage % ./sage -- | Sage Version 3.2, Release Date: 2008-11-20 | | Type notebook() for the GUI, and license() for information.| -- --- ImportError Traceback (most recent call last) /home/markus/sage/local/bin/sage-startup in module() 4 from sage.misc.interpreter import preparser, _ip 5 preparser(True) 6 import sage.all_cmdline 7 sage.all_cmdline._init_cmdline(globals()) 8 from sage.all import Integer, RealNumber /home/markus/sage/local/lib/python2.5/site-packages/sage/ all_cmdline.py in module() 12 try: 13 --- 14 from sage.all import * 15 from sage.calculus.predefined import x 16 preparser(on=True) /home/markus/sage/local/lib/python2.5/site-packages/sage/all.py in module() 84 from sage.functions.all import * 85 --- 86 import sage.symbolic.pynac # This must come before Calculus -- it initializes the Pynac library. 87 from sage.calculus.all import * 88 from sage.server.all import * ImportError: /home/markus/sage/local/lib/libpynac-0.1.so.1: symbol _ZNKSt5ctypeIcE13_M_widen_initEv, version GLIBCXX_3.4.11 not defined in file libstdc++.so.6 with link time reference WARNING: Failure executing file: /home/markus/sage/local/bin/sage- startup --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 21, 9:45 am, Octoploid [EMAIL PROTECTED] wrote: On Nov 20, 10:44 pm, William Stein [EMAIL PROTECTED] wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. I ran sage -upgrade on my system amd64, gcc 4.3.2. This is what I get after upgrading: SNIP ImportError: /home/markus/sage/local/lib/libpynac-0.1.so.1: symbol _ZNKSt5ctypeIcE13_M_widen_initEv, version GLIBCXX_3.4.11 not defined in file libstdc++.so.6 with link time reference WARNING: Failure executing file: /home/markus/sage/local/bin/sage- startup This seems to indicate that you upgraded from a binary build with a C+ + compiler using a different ABI. What did you upgrade from? Did you upgrade the C++ compiler since you last time build Sage? Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
I just compiled and ran make test on Mac OS X 10.5.5 on my MacBook 2.1GHz. All tests passed except, sage -t devel/sage/sage/misc/sageinspect.py ** File /Users/tjlahey/sage/devel/sage/sage/misc/sageinspect.py, line 93: sage: sage_getsource(sage.misc.sageinspect.sage_getfile) Exception raised: Traceback (most recent call last): File /Users/tjlahey/sage/local/bin/ncadoctest.py, line 1231, in run_one_test self.run_one_example(test, example, filename, compileflags) File /Users/tjlahey/sage/local/bin/sagedoctest.py, line 38, in run_one_example OrigDocTestRunner.run_one_example(self, test, example, filename, compileflags) File /Users/tjlahey/sage/local/bin/ncadoctest.py, line 1172, in run_one_example compileflags, 1) in test.globs File doctest __main__.example_0[24], line 1, in module sage_getsource(sage.misc.sageinspect.sage_getfile)###line 93: sage: sage_getsource(sage.misc.sageinspect.sage_getfile) File /Users/tjlahey/Downloads/sage-3.2/local/lib/python2.5/ site-packages/sage/misc/sageinspect.py, line 361, in sage_getsource File /Users/tjlahey/Downloads/sage-3.2/local/lib/python2.5/ site-packages/sage/misc/sageinspect.py, line 386, in sage_getsourcelines File /Users/tjlahey/Downloads/sage-3.2/local/lib/python2.5/ inspect.py, line 618, in getsourcelines lines, lnum = findsource(object) File /Users/tjlahey/Downloads/sage-3.2/local/lib/python2.5/ site-packages/IPython/ultraTB.py, line 151, in findsource IOError: could not get source code ** 1 items had failures: 1 of 27 in __main__.example_0 ***Test Failed*** 1 failures. For whitespace errors, see the file /Users/tjlahey/sage/ tmp/.doctest_sageinspect.py [3.4 s] exit code: 1024 -- The following tests failed: sage -t devel/sage/sage/misc/sageinspect.py One thing I noticed is that the directory, /Users/tjlahey/Downloads/sage-3.2/local/lib/python2.5/site-packages/ IPython/ doesn't exist any more since I moved the sage installation as one can see in the test, File /Users/tjlahey/sage/devel/sage/sage/misc/sageinspect.py, So, this appears to be a problem with the relocation scripts, I think. Thoughts? Suggestions? Cheers, Tim. --- Tim Lahey PhD Candidate, Systems Design Engineering University of Waterloo --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 21, 11:54 am, Tim Lahey [EMAIL PROTECTED] wrote: I just compiled and ran make test on Mac OS X 10.5.5 on my MacBook 2.1GHz. All tests passed except, SNIP The following tests failed: sage -t devel/sage/sage/misc/sageinspect.py One thing I noticed is that the directory, /Users/tjlahey/Downloads/sage-3.2/local/lib/python2.5/site-packages/ IPython/ doesn't exist any more since I moved the sage installation as one can see in the test, File /Users/tjlahey/sage/devel/sage/sage/misc/sageinspect.py, So, this appears to be a problem with the relocation scripts, I think. Thoughts? Suggestions? I think the problem here is easy-install.pth - which is an open issue - see #4317 - but I might be completely wrong here :) Cheers, Tim. Cheers, Michael --- Tim Lahey PhD Candidate, Systems Design Engineering University of Waterloo --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 20, 2008, at 1:44 PM, William Stein wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here: http://sagemath.org/src/ Or you can do sage -upgrade. Binaries and an official announcement should come within a day or two. Mac OS X, 10.5.5 (Dual Quad Xeon): - installed and built sage-3.2.rc2 w/o problems. - all tests passed! Then I upgraded (sage -upgrade) to 3.2 w/o problems, and moved the install tree to a different volume and did make test with -j6. All tests passed! Great work! Justin -- Justin C. Walker, Curmudgeon-at-Large () The ASCII Ribbon Campaign /\ Help Cure HTML Email --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 21, 7:51 pm, mabshoff [EMAIL PROTECTED] wrote: On Nov 21, 9:45 am, Octoploid [EMAIL PROTECTED] wrote: On Nov 20, 10:44 pm, William Stein [EMAIL PROTECTED] wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. I ran sage -upgrade on my system amd64, gcc 4.3.2. This is what I get after upgrading: SNIP ImportError: /home/markus/sage/local/lib/libpynac-0.1.so.1: symbol _ZNKSt5ctypeIcE13_M_widen_initEv, version GLIBCXX_3.4.11 not defined in file libstdc++.so.6 with link time reference WARNING: Failure executing file: /home/markus/sage/local/bin/sage- startup This seems to indicate that you upgraded from a binary build with a C+ + compiler using a different ABI. What did you upgrade from? Did you upgrade the C++ compiler since you last time build Sage? There was an old and unused version of /usr/lib/libstdc++.so on my system. Libpynac must somehow picked it up. I removed the library and rebuild sage. Now everything runs fine. BTW is there a way to pass -j3 to sage -upgrade ? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 21, 12:42 pm, Octoploid [EMAIL PROTECTED] wrote: On Nov 21, 7:51 pm, mabshoff [EMAIL PROTECTED] wrote: SNIP This seems to indicate that you upgraded from a binary build with a C+ + compiler using a different ABI. What did you upgrade from? Did you upgrade the C++ compiler since you last time build Sage? There was an old and unused version of /usr/lib/libstdc++.so on my system. Libpynac must somehow picked it up. I removed the library and rebuild sage. Now everything runs fine. Ok, that sounds about right :) BTW is there a way to pass -j3 to sage -upgrade ? export MAKE=make -j3 and then run sage -upgrade Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc2 released!
mabshoff wrote: Hello folks, here goes rc2 which fixes the last set of blockers left over from 3.2.rc1. it has been out for eight hours in IRC, but it seems like a good idea to announce it here. Aside from #4557 this should be it for patches merged into 3.2, so please build, test and report as usual. Sources and a sage.math only binary can be found in the usual spot in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Unless something goes very wrong we will release 3.2 tomorrow. If you like to participate in tomorrow's bug day you should use 3.2.rc2 as base. On Fedora 9, 32 bits: -- All tests passed! Total time for all tests: 5427.6 seconds Please see /home/jaap/downloads/sage-3.2.rc2/tmp/test.log for the complete log from this test. [EMAIL PROTECTED] sage-3.2.rc2]$ Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc2 released!
All tests passed on an intel mac, os 10.5. -M. Hampton On Nov 20, 5:10 am, Jaap Spies [EMAIL PROTECTED] wrote: mabshoff wrote: Hello folks, here goes rc2 which fixes the last set of blockers left over from 3.2.rc1. it has been out for eight hours in IRC, but it seems like a good idea to announce it here. Aside from #4557 this should be it for patches merged into 3.2, so please build, test and report as usual. Sources and a sage.math only binary can be found in the usual spot in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Unless something goes very wrong we will release 3.2 tomorrow. If you like to participate in tomorrow's bug day you should use 3.2.rc2 as base. On Fedora 9, 32 bits: -- All tests passed! Total time for all tests: 5427.6 seconds Please see /home/jaap/downloads/sage-3.2.rc2/tmp/test.log for the complete log from this test. [EMAIL PROTECTED] sage-3.2.rc2]$ Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc2 released!
Hi,
on Intel Core2 Duo MacBook OS X 10.4.11 / XCode 2.5 builds fine (with
'make -j2').
Running 'make -j2' test outputs some crap right about sage and
doc at the start:
{{{
sage-spkg sage-3.2.rc2
You must set the SAGE_ROOT environment variable or
run this script from the SAGE_ROOT or
SAGE_ROOT/local/bin/ directory.
sage-3.2.rc2
Machine:
Darwin susanne-webers-computer.local 8.11.1 Darwin Kernel Version
8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/
RELEASE_I386 i386 i386
sage: sage-3.2.rc2 is already installed
cd /Users/georgweber/Public/sage/sage-3.2.rc2 . local/bin/sage-env
cd local/bin/ ./sage-make_relative
Making script relocatable
sage-spkg doc-3.2.rc2
You must set the SAGE_ROOT environment variable or
run this script from the SAGE_ROOT or
SAGE_ROOT/local/bin/ directory.
doc-3.2.rc2
Machine:
Darwin susanne-webers-computer.local 8.11.1 Darwin Kernel Version
8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/
RELEASE_I386 i386 i386
sage: doc-3.2.rc2 is already installed
sage-spkg gap-4.4.10.p10 21
You must set the SAGE_ROOT environment variable or
run this script from the SAGE_ROOT or
SAGE_ROOT/local/bin/ directory.
gap-4.4.10.p10
Machine:
Darwin susanne-webers-computer.local 8.11.1 Darwin Kernel Version
8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/
RELEASE_I386 i386 i386
sage: gap-4.4.10.p10 is already installed
real0m0.434s
user0m0.105s
sys 0m0.273s
To install gap, gp, singular, etc., scripts
in a standard bin directory, start sage and
type something like
sage: install_scripts('/usr/local/bin')
at the SAGE command prompt.
SAGE build/upgrade complete!
}}}
but the finishes without failure:
{{{
All tests passed!
Total time for all tests: 6573.2 seconds
Please see /Users/georgweber/Public/sage/sage-3.2.rc2/tmp/test.log for
the complete log from this test.
}}}
Any ideas about what goes wrong right at the start of make test?
Issuing 'make -j2' testlong does not output the crap reported
above, and has only the two well known longstanding failures:
{{{
The following tests failed:
sage -t -long devel/sage/sage/crypto/mq/sr.py
sage -t -long devel/sage/sage/schemes/elliptic_curves/
ell_finite_field.py
Total time for all tests: 9534.8 seconds
}}}
(sr.py out of memory:
http://trac.sagemath.org/sage_trac/ticket/3758
ell_finite_field.py out of memory:
http://trac.sagemath.org/sage_trac/ticket/3760 )
Cheers,
gsw
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
Is there any difference from 3.2.rc2? -Marshall On Nov 20, 3:44 pm, William Stein [EMAIL PROTECTED] wrote: Hi, For early adopters, sage-3.2 has been released. You can get the source from here:http://sagemath.org/src/ Or you can do sage -upgrade. Binaries and an official announcement should come within a day or two. William -- William Stein Associate Professor of Mathematics University of Washingtonhttp://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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Nov 20, 2:16 pm, mhampton [EMAIL PROTECTED] wrote: Is there any difference from 3.2.rc2? -Marshall Three patches in the Sage library as well as a fix for the ext repo, so upgrading is highly recommended. Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: sage-3.2
On Thu, Nov 20, 2008 at 2:20 PM, mabshoff [EMAIL PROTECTED] wrote: On Nov 20, 2:16 pm, mhampton [EMAIL PROTECTED] wrote: Is there any difference from 3.2.rc2? -Marshall Three patches in the Sage library as well as a fix for the ext repo, so upgrading is highly recommended. You can also do sage: hg_sage.pull() sage: hg_doc.pull() sage: hg_scripts.pull() Then sage -br to upgrade more quickly. William --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
On Nov 15, 2008, at 03:15 , mabshoff wrote: Hello folks, here goes the slightly delayed 3.2.rc1 with some goodies from SD 11 as well as various fixes from Bug Day 16. There are actually *four* segfault fixes in this build. On top the cleanup up build system, i.e. massive speedups to dependency tracking and cleanups of setup.py, are in and it should be much more stable since at least the most obvious kinks have been ironed out. We are still having some issues with numerical noise, but since the pickle jar and a couple other blockers are outstanding we will see an rc2 hopefully before the weekend is over. Sources as well as a sage.math only binary are in the usual location at http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Built w/o problems on Mac OS X, 10.4.11 (Core 2 Duo). Testing showed the usual suspect :-} sage -t devel/sage/sage/matrix/matrix_double_dense.pyx ** File /Users/tmp/sage-3.2.rc1/devel/sage/sage/matrix/ matrix_double_dense.pyx, line 444: sage: ~A Expected: Traceback (most recent call last): ... LinAlgError: singular matrix Got: [-4.50359962737e+15 9.00719925474e+15 -4.50359962737e+15] [ 9.00719925474e+15 -1.80143985095e+16 9.00719925474e+15] [-4.50359962737e+15 9.00719925474e+15 -4.50359962737e+15] ** 1 items had failures: 1 of 11 in __main__.example_15 ***Test Failed*** 1 failures. Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Absorption of Federal Funds If you're not confused, You're not paying attention --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
I had one doctest failure on a 32-bit ubuntu laptop: sage -t devel/sage/sage/combinat/species/library.py ** File /home/john/sage-3.2.rc1/devel/sage/sage/combinat/species/library.py, line 86: sage: a.automorphism_group() Expected: Permutation Group with generators [(), ()] Got: Permutation Group with generators [()] ** 1 items had failures: 1 of 9 in __main__.example_1 John 2008/11/15 mabshoff [EMAIL PROTECTED]: Hello folks, here goes the slightly delayed 3.2.rc1 with some goodies from SD 11 as well as various fixes from Bug Day 16. There are actually *four* segfault fixes in this build. On top the cleanup up build system, i.e. massive speedups to dependency tracking and cleanups of setup.py, are in and it should be much more stable since at least the most obvious kinks have been ironed out. We are still having some issues with numerical noise, but since the pickle jar and a couple other blockers are outstanding we will see an rc2 hopefully before the weekend is over. Sources as well as a sage.math only binary are in the usual location at http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Please build, doctest and report errors as usual. Make sure to check the open issues for 3.2. If you open any neew tickets make sure that they are critical or higher if you assign them against 3.2. Any ticket without a patch will get bumped since 3.2 needs to be shoved out the door :) Cheers, Michael Merged in Sage 3.2.rc1: #3761: William Stein: warning when run sage binary if the processor instruction set doesn't support everything that was on the machine where sage was built [Reviewed by Georg Weber, Michael Abshoff] #4190: David Loeffler: division of number field order elements doesn't check for membership [Reviewed by John Cremona, Robert Bradshaw] #4249: John Cremona, John Voight, Craig Citro: Inconsistency in number field integral bases [Reviewed by Craig Citro, John Cremona, John Voight] #4278: Robert Bradshaw, Mike Hansen: Old parent's don't correctly handle coerce maps from Python's native types [Reviewed by Burcin Erocal] #4329: William Stein: class numbers of non-maximal orders -- should return NotImplementedError for now [Reviewed by Dan Shumow] #4392: John Cremona: smallest_integer() is broken [Reviewed by David Loeffler] #4466: William Stein: fix det in linbox case to fail if proof=False isn't also set [Reviewed by Robert Bradshaw] #4447: Jason Grout: graph attributes (_boundary, _pos, etc.) are not updated properly [Reviewed by Robert Miller] #4480: Robert Bradshaw, Gonzalo Tonaria, Craig Citro: cython dependancy checking is too slow [Reviewed by Robert Bradshaw, Michael Abshoff] #4485: Robert Bradshaw: notebook -- implicit multiplication is broken in the notebook but works on the command line [Reviewed by William Stein] #4499: Mike Hansen: Fix latex for sech and csch [Reviewed by William Stein] #4500: Craig Citro: cython files missing from build directory after install [Reviewed by Georg Weber, Michael Abshoff, Robert Bradshaw] #4503: John Palmieri: numerical noise in matrix_double_dense on intel mac os X 10.5: SVD [Reviewed by Michael Abshoff] #4505: Jason Grout: planarity code mishandles graphs with no edges (segfault) [Reviewed by Michael Abshoff] #4506: Jason Grout: planarity ignores error code when adding edge [Reviewed by Robert Bradshaw] #4507: Jason Grout: compile warning for planarity code [Reviewed by Michael Abshoff] #4510: Jason Grout: Add references for Boyer's planarity code implementation [Reviewed by Minh Nguyen] #4511: Franco Saliola: sage-combinat script won't work with two digit version numbers (for example: 3.2) [Reviewed by Nicolas Thiery] #4512: Craig Citro: sage path-related troubles [Reviewed by Michael Abshoff] #4515: William Stein: make it so make check runs Sage once before running itself, to ensure that sage-location is called, and that sage works [Reviewed by Georg Weber] #4516: William Stein: make check on binaries should smoothly 100% pass -- right now it fails on the docs and gives lots of verbosity at the start [Reviewed by Georg Weber] #4519: Craig Citro: problem with build code [Reviewed by Georg Weber] #4520: Robert Bradshaw: segfault in cyclotomic matrices [Reviewed by Craig Citro] #4526: Mike Hansen: Can't multiply symmetric functions by 0 [Reviewed by Jason Bandlow] #4527: William Stein: Exception in 'sage.matrix.matrix_integer_dense.Matrix_integer_dense._hnf_modn_impl' [Reviewed by Craig Citro] --~--~-~--~~~---~--~~ 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
[sage-devel] Re: Sage 3.2.rc1 released
John Cremona wrote: I had one doctest failure on a 32-bit ubuntu laptop: sage -t devel/sage/sage/combinat/species/library.py ** File /home/john/sage-3.2.rc1/devel/sage/sage/combinat/species/library.py, line 86: sage: a.automorphism_group() Expected: Permutation Group with generators [(), ()] Got: Permutation Group with generators [()] ** 1 items had failures: 1 of 9 in __main__.example_1 Same for me on Fedora 9, 32 bits Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
On intel mac running 10.5, four tests failed with sage -testall -long, all of which are known issues: wester.py numerical noise http://trac.sagemath.org/sage_trac/ticket/ 4472 matrix_double_dense numerical noise http://trac.sagemath.org/ sage_trac/ticket/4502 sr.py out of memory http://trac.sagemath.org/sage_trac/ticket/3758 ell_finite_field.py out of memory http://trac.sagemath.org/sage_trac/ ticket/3760 John --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
On Nov 15, 8:25 am, John Cremona [EMAIL PROTECTED] wrote: I had one doctest failure on a 32-bit ubuntu laptop: sage -t devel/sage/sage/combinat/species/library.py ** File /home/john/sage-3.2.rc1/devel/sage/sage/combinat/species/library.py, line 86: sage: a.automorphism_group() Expected: Permutation Group with generators [(), ()] Got: Permutation Group with generators [()] ** 1 items had failures: 1 of 9 in __main__.example_1 This is a new one in trac and I have made this ticket #4531 - a blocker for 3.2. John Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
mabshoff wrote: On Nov 15, 8:25 am, John Cremona [EMAIL PROTECTED] wrote: I had one doctest failure on a 32-bit ubuntu laptop: sage -t devel/sage/sage/combinat/species/library.py ** File /home/john/sage-3.2.rc1/devel/sage/sage/combinat/species/library.py, line 86: sage: a.automorphism_group() Expected: Permutation Group with generators [(), ()] Got: Permutation Group with generators [()] ** 1 items had failures: 1 of 9 in __main__.example_1 This is a new one in trac and I have made this ticket #4531 - a blocker for 3.2. John Cheers, This was already in rc0: On Fedora 8, 32 bits one test failure: [EMAIL PROTECTED] sage-3.2.rc0]$ ./sage -t devel/sage/sage/combinat/species/library.py sage -t devel/sage/sage/combinat/species/library.pysage -t devel/sage/sage/combinat/species/library.pysage -t devel/sage/sage/combinat/species/library.py** File /home/jaap/Download/sage-3.2.rc0/devel/sage/sage/combinat/species/library.py, line 86: sage: a.automorphism_group() Expected: Permutation Group with generators [(), ()] Got: Permutation Group with generators [()] ** 1 items had failures: 1 of 9 in __main__.example_1 ***Test Failed*** 1 failures. For whitespace errors, see the file /home/jaap/Download/sage-3.2.rc0/tmp/.doctest_library.py [11.5 s] exit code: 1024 -- The following tests failed: sage -t devel/sage/sage/combinat/species/library.py Total time for all tests: 11.5 seconds Jaap Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
On Nov 15, 12:25 pm, Jaap Spies [EMAIL PROTECTED] wrote: Hi Jaap, This was already in rc0: Yes, I do remember, but we did not open a ticket then :) SNIP Jaap Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
2008/11/15 mabshoff [EMAIL PROTECTED]: On Nov 15, 8:25 am, John Cremona [EMAIL PROTECTED] wrote: I had one doctest failure on a 32-bit ubuntu laptop: sage -t devel/sage/sage/combinat/species/library.py ** File /home/john/sage-3.2.rc1/devel/sage/sage/combinat/species/library.py, line 86: sage: a.automorphism_group() Expected: Permutation Group with generators [(), ()] Got: Permutation Group with generators [()] ** 1 items had failures: 1 of 9 in __main__.example_1 This is a new one in trac and I have made this ticket #4531 - a blocker for 3.2. All tests passed on 64-bit ubuntu: Linux version 2.6.24-19-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:15:37 UTC 2008 in case that helps debugging! John Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
All tests passed gutsy x86_64 On Nov 15, 3:15 am, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here goes the slightly delayed 3.2.rc1 with some goodies from SD 11 as well as various fixes from Bug Day 16. There are actually *four* segfault fixes in this build. On top the cleanup up build system, i.e. massive speedups to dependency tracking and cleanups of setup.py, are in and it should be much more stable since at least the most obvious kinks have been ironed out. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
Hi, on Intel Mac OS X 10.4.11 / XCode 2.5 only three of these: On 15 Nov., 21:07, John H Palmieri [EMAIL PROTECTED] wrote: On intel mac running 10.5, four tests failed with sage -testall -long, all of which are known issues: wester.py numerical noise http://trac.sagemath.org/sage_trac/ticket/ 4472 matrix_double_dense numerical noise http://trac.sagemath.org/ sage_trac/ticket/4502 sr.py out of memory http://trac.sagemath.org/sage_trac/ticket/3758 ell_finite_field.py out of memory http://trac.sagemath.org/sage_trac/ ticket/3760 (testlong) tests fail: wester.py has no numerical noise on my box. The other three reported ones do occur. (The test run is now at elliptic_curves/padic_lseries.py, I'll post another message if more failures occur, which I do not expect.) Cheers, gsw John --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
On Nov 15, 2008, at 03:15 , mabshoff wrote: Hello folks, here goes the slightly delayed 3.2.rc1 with some goodies from SD 11 as well as various fixes from Bug Day 16. There are actually *four* segfault fixes in this build. On top the cleanup up build system, i.e. massive speedups to dependency tracking and cleanups of setup.py, are in and it should be much more stable since at least the most obvious kinks have been ironed out. We are still having some issues with numerical noise, but since the pickle jar and a couple other blockers are outstanding we will see an rc2 hopefully before the weekend is over. Sources as well as a sage.math only binary are in the usual location at http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Built w/o problems on Mac OS X, 10.5.5 (Dual Quad Xeon). Testing showed two failures, as follows. Should I file bug reports? Justin sage -t devel/sage/sage/calculus/wester.py: ** File /Users/tmp/sage-3.2.rc1/devel/sage/sage/calculus/wester.py, line 261: : [float(f(i/10)) for i in range(1,5)] Expected: BLANKLINE [-0.00033670040754082975, -0.0027778004096620235, -0.00989099409140..., -0.025411145508414...] Got: [-0.00033670040754081587, -0.0027778004096621622, -0.0098909940914039818, -0.025411145508414779] ** 1 items had failures: 1 of 193 in __main__.example_0 ***Test Failed*** 1 failures. sage -t devel/sage/sage/matrix/matrix_double_dense.pyx: ** File /Users/tmp/sage-3.2.rc1/devel/sage/sage/matrix/ matrix_double_dense.pyx, line 444: sage: ~A Expected: Traceback (most recent call last): ... LinAlgError: singular matrix Got: [-4.50359962737e+15 9.00719925474e+15 -4.50359962737e+15] [ 9.00719925474e+15 -1.80143985095e+16 9.00719925474e+15] [-4.50359962737e+15 9.00719925474e+15 -4.50359962737e+15] ** 1 items had failures: 1 of 11 in __main__.example_15 Justin -- Justin C. Walker Curmudgeon-at-large -- Network, n., Difference between work charged for and work done --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
On Nov 15, 3:36 pm, Justin C. Walker [EMAIL PROTECTED] wrote: SNIP Built w/o problems on Mac OS X, 10.5.5 (Dual Quad Xeon). Testing showed two failures, as follows. Should I file bug reports? Both are known failures with tickets, so no need to do anything besides fixing them :) Justin Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc1 released
On Nov 15, 2008, at 15:39 , mabshoff wrote: On Nov 15, 3:36 pm, Justin C. Walker [EMAIL PROTECTED] wrote: SNIP Built w/o problems on Mac OS X, 10.5.5 (Dual Quad Xeon). Testing showed two failures, as follows. Should I file bug reports? Both are known failures with tickets, so no need to do anything besides fixing them :) #4502 requires an updated scipy, but Jason suggests a hack of checking the scipy determinant for zero before inverting (the Sage-supplied determinant tests out between 10e-17 and 10e-16). I'm not a doctest maven, so I'm not sure how to handle such a doctest. Is there doc for controlling doctests? #4472 seems simple enough: just replace low-order digits with '.' (a handy tool, the '.'-key :-}). I picked 4 digits for each untouched value (which worked). Thanks for pointers! Justin -- Justin C. Walker Curmudgeon at Large Director Institute for the Enhancement of the Director's Income -- Build a man a fire and he'll be warm for a night. Set a man on fire and he'll be warm for the rest of his life. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
I know this is late, but all tests passed and the build went fine on
my work machine, which runs amd64 hardy heron.
On Tue, Nov 11, 2008 at 7:24 AM, mabshoff [EMAIL PROTECTED] wrote:
Hello folks,
here is 3.2.rc0 and I have to confess that I cheated: I did build this
on numerous platforms before announcing here (if you hung out in IRC
you knew about this release for about 6 hours now) and as it turns out
my caution was justified. Doctesting is broken with this release
unless you do the following:
./sage -sh
cd local/bin
hg update -C
After doing that doctesting works again. The issue is (again) releated
to -sdist and I should have a fix in rc1 shortly. The initial plan has
been shifted by about 5 days, so expect a releae by Thursday. We
merged some major features in rc0, specifically the new timeit doctest
code as well as Cython 0.10 and the RDF/CDF backend switch to numpy.
Expect some numerical noise doctest failures and some other related
known issues. Please report issues here and check trac for existing
tickerts. There was also some major setup.py surgery, so please report
any Sage library build issue. sage -b should be much faster and less
buggy than before, but ;) One issue you will see here is that we
no longer suppress warnings, so expect sage -b to be more noise.
While most of those are caused by Cython's code generator due to
unused variables there is definitely some stuff in there worth fixing.
If the noise level is too annoying we can turn on warning suppression
by default again.
Sources and a sage.math only binary can be found at
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/
Cheers,
Michael
Merged in Sage 3.2.rc0:
#3310: Craig Citro, Gonzalo Tonaria: sage -b fails after touching
sage/libs/mwrank/{mwrank.pyx,wrap.cc} [Reviewed by Michael Abshoff]
#3476: Nick Alexander, Mike Hansen: save timeit information with sage -
t -timeit [Reviewed by Mike Hansen, Michael Abshoff]
#3498: Jason Grout: make numpy the backend for matrices over CDF and
RDF [Reviewed by Mike Hansen, Robert Bradshaw, Michael Abshoff]
#3580: Craig Citro, John Voight: ensure that totallyreal does not
import numpy on startup [Reviewed by John Voight, Craig Citro]
#3750: Karl-Dieter Crisman: Request for a log function for Sage
integers [Reviewed by Mike Hansen]
#4362: Dan Bump: Bug fixes in tableaux latex output [Reviewed by Mike
Hansen, Nicolas Thiery]
#4395: William Stein: Sage 3.1.4: magma related optional doctest
failure in sage/rings/quotient_ring.py [Reviewed by Michael Abshoff]
#4425: Karl-Dieter Crisman: sqrt(4) returns a SymbolicComposition
instead of the number 2! [Reviewed by William Stein]
#4443: Craig Citro: Massive prime_range speedup, arith* files cleanup
[Reviewed by John Cremona]
#: Craig Citro: Remove duplicate source names in setup.py
[Reviewed by Michael Abshoff]
#4448: Jason Grout: bug in interact with matrices [Reviewed by Mike
Hansen]
#4452: William Stein: optimize next_prime [Reviewed by Robert
Bradshaw]
#4455: Nicolas Thiery: bug in Coxeter matrix for type G2 [Reviewed by
Mike Hansen]
#4462: John Perry, Jason Grout: contour_plot defaults changed to fill,
affects implicit_plot [Reviewed by Mike Hansen]
#4467: Michael Abshoff: removed unused hanke library code [Reviwed by
Jon Hanke]
#4473: William Stein: loading file.sage that has a line load foo.py
is broken due to a missing import [Reviewed by Michael Abshoff]
#4476: Robert Bradshaw: Update to Cython 0.10 [Reviewed by Michael
Abshoff]
#4479: Timothy Clemans: sage/logic/logic.py contains a trivial typo:
varaiable [Reviewed by Minh Nguyen]
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
sage: numpy.linalg.inv(a) array([[ 2.25125019e+15, -4.50250038e+15, 2.25125019e+15], [ -4.50250038e+15, 9.00500077e+15, -4.50250038e+15], [ 2.25125019e+15, -4.50250038e+15, 2.25125019e+15]]) I get this: sage: scipy.linalg.inv(a) array([[ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15], [ 9.00719925e+15, -1.80143985e+16, 9.00719925e+15], [ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15]]) Some notes: Scipy uses numpy as its backend The numerical noise problem is probably something deeper, because it doesn't affect only the results of inv(), but others as well, like when trying to get the autovalues matrix after obtaining the eigenvectors matrix. In Ipython: In [34]: from pylab import * In [35]: k = array([[1,2,4],[4,7,5],[8,7,9]],dtype='float64') In [36]: lambdas, P = eig(k) In [37]: dot(P.T,dot(k,P)) Out[37]: array([[ 16.47731777, 0.48505536, -0.12297265], [ -4.20177431, -1.90215152, 0.03248141], [ -0.8356282 , -0.02547992, 2.42483375]]) In [38]: lambdas Out[38]: array([ 16.47731777, -1.90215152, 2.42483375]) One can see the main diagonal fits the autovalues right, but the other elements should be zero, when one of them gets to a significant value (-4 is even greater in modulus than two of the autovalues) Ronan --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
Hi all, So there's one annoying new problem with rc0, and it's partly my fault. Here's the issue: if you do a fresh build, and then clone, it's going to do a sage -ba. The underlying problem is coming from the way trac #4500 (which is a genuine bug) interacts with our new build system. I'll fix it in the morning, but if you want to use rc0 in the interim, here's an easy workaround: type sage -b, and hit ctrl-c as soon as it's done copying files over. Then cd $SAGE_ROOT/devel/sage-main/build, and do: find . -name *.o | xargs touch What those two commands together do is copy all the cython files in the sage library into the build directory, and then touch the object files so nothing needs rebuilt. This is fine, because if you've built from source, you just built all these files anyway. Once you do this once, everything is back to normal. -cc --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
John H Palmieri wrote: Expect some numerical noise doctest failures and some other related known issues. Please report issues here and check trac for existing tickets. On an intel mac running 10.5 (after changing my stone-age shell :), sage -testall has two or three problems: the known numerical noise problem in wester.py (http:// trac.sagemath.org/sage_trac/ticket/4472) an error in matrix_double_dense, which I couldn't find on trac (should I create a ticket?): sage -t devel/sage/sage/matrix/matrix_double_dense.pyx ** File /Applications/sage/devel/sage/sage/matrix/ matrix_double_dense.pyx, line 444: sage: ~A Expected: Traceback (most recent call last): ... LinAlgError: singular matrix Got: [-4.50359962737e+15 9.00719925474e+15 -4.50359962737e+15] [ 9.00719925474e+15 -1.80143985095e+16 9.00719925474e+15] [-4.50359962737e+15 9.00719925474e+15 -4.50359962737e+15] Hmm. This code was just moved to a numpy backend. Scipy correctly saw this matrix as singular on my system. However, it looks like you are seeing a spurious inverse, most likely due to numerical issues. Could you post the output of the following commands: sage: A = matrix(RDF,3,range(1,10));A sage: A.determinant() sage: ~A sage: b=A.numpy(); b sage: import scipy sage: import scipy.linalg sage: scipy.linalg.det(b) sage: scipy.linalg.inv(b) ** File /Applications/sage/devel/sage/sage/matrix/ matrix_double_dense.pyx, line 909: sage: max((U*S*V.transpose()-m).list())1e-15 # check Expected: True Got: False Again, could you post the output of the following commands: sage: m = matrix(RDF,3,2,range(6)); m sage: U,S,V = m.SVD() sage: U*S*V.transpose() # random low order bits Thanks, Jason --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
John H Palmieri wrote: On Nov 12, 6:41 am, Jason Grout [EMAIL PROTECTED] wrote: John H Palmieri wrote: an error in matrix_double_dense, which I couldn't find on trac (should I create a ticket?): Yes, please create tickets for both of these errors. sage: scipy.linalg.det(b) 0.0 sage: scipy.linalg.inv(b) array([[ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15], [ 9.00719925e+15, -1.80143985e+16, 9.00719925e+15], [ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15]]) That last pair of results looks suspicious, doesn't it? Yes, very much so. Any comments from anyone on what might be going on? I wonder if it is a 32/64 bit issue. I'll submit this to the numpy list as well. max((U*S*V.transpose()-m).list()) 1.7763568394e-15 Okay, apparently the doctest just needs a looser bound; what you get is still within reason for numerical issues. Currently we see if that maximum is 1e-15. Changing it to 1e-14 should fix this. Jason --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
On Nov 12, 8:20 am, Jason Grout [EMAIL PROTECTED] wrote: John H Palmieri wrote: On Nov 12, 6:41 am, Jason Grout [EMAIL PROTECTED] wrote: John H Palmieri wrote: an error in matrix_double_dense, which I couldn't find on trac (should I create a ticket?): Yes, please create tickets for both of these errors. http://trac.sagemath.org/sage_trac/ticket/4502 http://trac.sagemath.org/sage_trac/ticket/4503 John --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
John H Palmieri wrote: On Nov 12, 6:41 am, Jason Grout [EMAIL PROTECTED] wrote: John H Palmieri wrote: an error in matrix_double_dense, which I couldn't find on trac (should I create a ticket?): sage -t devel/sage/sage/matrix/matrix_double_dense.pyx ** File /Applications/sage/devel/sage/sage/matrix/ matrix_double_dense.pyx, line 444: sage: ~A Expected: Traceback (most recent call last): ... LinAlgError: singular matrix Got: [-4.50359962737e+15 9.00719925474e+15 -4.50359962737e+15] [ 9.00719925474e+15 -1.80143985095e+16 9.00719925474e+15] [-4.50359962737e+15 9.00719925474e+15 -4.50359962737e+15] Hmm. This code was just moved to a numpy backend. Scipy correctly saw this matrix as singular on my system. However, it looks like you are seeing a spurious inverse, most likely due to numerical issues. Could you post the output of the following commands: sage: A = matrix(RDF,3,range(1,10));A sage: A.determinant() sage: ~A sage: b=A.numpy(); b sage: import scipy sage: import scipy.linalg sage: scipy.linalg.det(b) sage: scipy.linalg.inv(b) sage: A = matrix(RDF,3,range(1,10));A [1.0 2.0 3.0] [4.0 5.0 6.0] [7.0 8.0 9.0] sage: A.determinant() 0.0 sage: -A [-1.0 -2.0 -3.0] [-4.0 -5.0 -6.0] [-7.0 -8.0 -9.0] sage: b = A.numpy(); b array([[ 1., 2., 3.], [ 4., 5., 6.], [ 7., 8., 9.]]) sage: import scipy sage: import scipy.linalg sage: scipy.linalg.det(b) 0.0 sage: scipy.linalg.inv(b) array([[ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15], [ 9.00719925e+15, -1.80143985e+16, 9.00719925e+15], [ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15]]) That last pair of results looks suspicious, doesn't it? One more time, could you do the following sequence of commands so that I can report them to the numpy mailing list. I've left the output from my run; it's interesting that the numpy.linalg.inv on my computer gives the same ridiculous answers that your scipy.linalg.inv command gives. It looks like it is scaling by dividing by the determinant or something. sage: import numpy sage: a=numpy.array([[1,2,3],[4,5,6],[7,8,9]],dtype=float64) sage: import scipy sage: import scipy.linalg sage: import numpy.linalg sage: scipy.linalg.det(a) 0.0 sage: scipy.linalg.inv(a) --- LinAlgError Traceback (most recent call [snip] LinAlgError: singular matrix sage: numpy.linalg.det(a) -1.3325928902019335e-15 sage: numpy.linalg.inv(a) array([[ 2.25125019e+15, -4.50250038e+15, 2.25125019e+15], [ -4.50250038e+15, 9.00500077e+15, -4.50250038e+15], [ 2.25125019e+15, -4.50250038e+15, 2.25125019e+15]]) Thanks, Jason --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
Actually, I have a numpy question, and since we're on the topic ... The following is somewhat frustrating: sage: R = RDF['x'] sage: f = R([4, 4, 1, 4, 2, 0, 1]) sage: f.roots(algorithm='pari') [(-1.0, 1), (-1.0, 1)] sage: f.roots() # uses numpy [] sage: import numpy sage: numpy.roots(f.reverse().list()) array([ 0.5001 +1.32287567e+00j, 0.5001 -1.32287567e+00j, 0.4999 +1.32287564e+00j, 0.4999 -1.32287564e+00j, -1. +1.79471980e-08j, -1. -1.79471980e-08j]) I assume this comes down to the following: sage: [ numpy.isreal(x) for x in numpy.roots(f.reverse().list()) ] [False, False, False, False, False, False] What's the easiest parameter to adjust so that we get those roots? Note: this polynomial is clearly bad for a certain reason, namely that it's the square of another polynomial. -cc --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
John H Palmieri wrote: On Nov 11, 12:07 pm, mabshoff [EMAIL PROTECTED] wrote: On Nov 11, 12:02 pm, John H Palmieri [EMAIL PROTECTED] wrote: On Nov 11, 11:57 am, Jaap Spies [EMAIL PROTECTED] wrote: John H Palmieri wrote: On Nov 11, 4:24 am, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here is 3.2.rc0 and I have to confess that I cheated: I did build this on numerous platforms before announcing here (if you hung out in IRC you knew about this release for about 6 hours now) and as it turns out my caution was justified. Doctesting is broken with this release unless you do the following: ./sage -sh cd local/bin hg update -C When I try to do the last line (on an intel mac running 10.5), I get this: abort: could not import module lookup! Did I do something wrong? do: ./sage -sh cd local/bin ./hg update -C Here's what happens: (/Applications/sage) [11:26am] ./sage -sh Starting subshell with Sage environment variables set. Be sure to exit when you are done and do not do anything with other copies of Sage! So far so good. (/Applications/sage) [11:58am] cd local/bin (...local/bin) [11:58am] ./hg update -C abort: could not import module lookup! mmh - can you try without the ./ since hg is in $PATH. I did that first, same problem. What shell are you using - even though this should not matter, but one never knows. Oh, this is the problem. I'm running tcsh (I got used to it years ago, and keep deciding it's too much work to switch). When I switch to bash, everything works. I get the same error (using bash) when trying to doctest a file: $ sage -t graph.py sage -t devel/sage-main/sage/graphs/graph.py Traceback (most recent call last): File /home/jason/sage/tmp/.doctest_graph.py, line 6598, in module import sagedoctest ImportError: No module named sagedoctest [4.6 s] exit code: 1024 -- The following tests failed: sage -t devel/sage-main/sage/graphs/graph.py Total time for all tests: 4.6 seconds I built sage 3.2.rc0 from scratch. Jason --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
On Nov 12, 4:28 pm, Jason Grout [EMAIL PROTECTED] wrote: John H Palmieri wrote: SNIP Oh, this is the problem. I'm running tcsh (I got used to it years ago, and keep deciding it's too much work to switch). When I switch to bash, everything works. I get the same error (using bash) when trying to doctest a file: $ sage -t graph.py sage -t devel/sage-main/sage/graphs/graph.py Traceback (most recent call last): File /home/jason/sage/tmp/.doctest_graph.py, line 6598, in module import sagedoctest ImportError: No module named sagedoctest [4.6 s] exit code: 1024 Did you do the hg update -H in the local/bin repo? Cheers, Michael -- The following tests failed: sage -t devel/sage-main/sage/graphs/graph.py Total time for all tests: 4.6 seconds I built sage 3.2.rc0 from scratch. Jason --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
One more time, could you do the following sequence of commands so that I can report them to the numpy mailing list. I've left the output from my run; it's interesting that the numpy.linalg.inv on my computer gives the same ridiculous answers that your scipy.linalg.inv command gives. It looks like it is scaling by dividing by the determinant or something. sage: import numpy sage: a=numpy.array([[1,2,3],[4,5,6],[7,8,9]],dtype=float64) sage: import scipy sage: import scipy.linalg sage: import numpy.linalg sage: scipy.linalg.det(a) 0.0 sage: scipy.linalg.inv(a) --- LinAlgError Traceback (most recent call [snip] LinAlgError: singular matrix sage: numpy.linalg.det(a) -1.3325928902019335e-15 sage: numpy.linalg.inv(a) array([[ 2.25125019e+15, -4.50250038e+15, 2.25125019e+15], [ -4.50250038e+15, 9.00500077e+15, -4.50250038e+15], [ 2.25125019e+15, -4.50250038e+15, 2.25125019e+15]]) I get this: sage: scipy.linalg.det(a) 0.0 sage: scipy.linalg.inv(a) array([[ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15], [ 9.00719925e+15, -1.80143985e+16, 9.00719925e+15], [ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15]]) sage: numpy.linalg.det(a) 6.6613381477509392e-16 sage: numpy.linalg.inv(a) array([[ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15], [ 9.00719925e+15, -1.80143985e+16, 9.00719925e+15], [ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15]]) John --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
mabshoff wrote: On Nov 12, 4:28 pm, Jason Grout [EMAIL PROTECTED] wrote: John H Palmieri wrote: SNIP Oh, this is the problem. I'm running tcsh (I got used to it years ago, and keep deciding it's too much work to switch). When I switch to bash, everything works. I get the same error (using bash) when trying to doctest a file: $ sage -t graph.py sage -t devel/sage-main/sage/graphs/graph.py Traceback (most recent call last): File /home/jason/sage/tmp/.doctest_graph.py, line 6598, in module import sagedoctest ImportError: No module named sagedoctest [4.6 s] exit code: 1024 Did you do the hg update -H in the local/bin repo? Oops, that took care of it. Sorry for the noise. Jason --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
John H Palmieri wrote: sage: scipy.linalg.det(a) 0.0 sage: scipy.linalg.inv(a) array([[ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15], [ 9.00719925e+15, -1.80143985e+16, 9.00719925e+15], [ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15]]) sage: numpy.linalg.det(a) 6.6613381477509392e-16 sage: numpy.linalg.inv(a) array([[ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15], [ 9.00719925e+15, -1.80143985e+16, 9.00719925e+15], [ -4.50359963e+15, 9.00719925e+15, -4.50359963e+15]]) I was about to post to the appropriate mailing list, but realized that we never updated scipy (I thought we had). That means we are running scipy code from over a year ago. Now, they haven't had a new release in over a year, but we should probably update to SVN at least before complaining about this error. For now, we can check to see if the determinant (the scipy.linalg.det determinant) is zero. If it is, throw the singular matrix error. Jason --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
On Nov 11, 4:24 am, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here is 3.2.rc0 and I have to confess that I cheated: I did build this on numerous platforms before announcing here (if you hung out in IRC you knew about this release for about 6 hours now) and as it turns out my caution was justified. Doctesting is broken with this release unless you do the following: ./sage -sh cd local/bin hg update -C When I try to do the last line (on an intel mac running 10.5), I get this: abort: could not import module lookup! Did I do something wrong? John --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
On Nov 11, 11:27 am, John H Palmieri [EMAIL PROTECTED] wrote: On Nov 11, 4:24 am, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here is 3.2.rc0 and I have to confess that I cheated: I did build this on numerous platforms before announcing here (if you hung out in IRC you knew about this release for about 6 hours now) and as it turns out my caution was justified. Doctesting is broken with this release unless you do the following: ./sage -sh cd local/bin hg update -C When I try to do the last line (on an intel mac running 10.5), I get this: abort: could not import module lookup! Hmm, this is strange to say the least. Could you post more of a backtrace if there is one? In case you have a system wide hg (or one from another Sage install) you could try to use that. Did I do something wrong? John Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
John H Palmieri wrote: On Nov 11, 4:24 am, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here is 3.2.rc0 and I have to confess that I cheated: I did build this on numerous platforms before announcing here (if you hung out in IRC you knew about this release for about 6 hours now) and as it turns out my caution was justified. Doctesting is broken with this release unless you do the following: ./sage -sh cd local/bin hg update -C When I try to do the last line (on an intel mac running 10.5), I get this: abort: could not import module lookup! Did I do something wrong? do: ./sage -sh cd local/bin ./hg update -C then exit make check Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
On Nov 11, 11:57 am, Jaap Spies [EMAIL PROTECTED] wrote: John H Palmieri wrote: On Nov 11, 4:24 am, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here is 3.2.rc0 and I have to confess that I cheated: I did build this on numerous platforms before announcing here (if you hung out in IRC you knew about this release for about 6 hours now) and as it turns out my caution was justified. Doctesting is broken with this release unless you do the following: ./sage -sh cd local/bin hg update -C When I try to do the last line (on an intel mac running 10.5), I get this: abort: could not import module lookup! Did I do something wrong? do: ./sage -sh cd local/bin ./hg update -C Here's what happens: (/Applications/sage) [11:26am] ./sage -sh Starting subshell with Sage environment variables set. Be sure to exit when you are done and do not do anything with other copies of Sage! (/Applications/sage) [11:58am] cd local/bin (...local/bin) [11:58am] ./hg update -C abort: could not import module lookup! then exit make check As you might guess, doctesting fails at this point: ImportError: No module named sagedoctest Maybe I'll start over again from the tar file. John --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
Jaap Spies wrote: John H Palmieri wrote: On Nov 11, 4:24 am, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here is 3.2.rc0 and I have to confess that I cheated: I did build this on numerous platforms before announcing here (if you hung out in IRC you knew about this release for about 6 hours now) and as it turns out my caution was justified. Doctesting is broken with this release unless you do the following: ./sage -sh cd local/bin hg update -C When I try to do the last line (on an intel mac running 10.5), I get this: abort: could not import module lookup! Did I do something wrong? do: ../sage -sh cd local/bin ../hg update -C sorry typo ./hg update -C Jaap then exit make check Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
On Nov 11, 12:07 pm, mabshoff [EMAIL PROTECTED] wrote: On Nov 11, 12:02 pm, John H Palmieri [EMAIL PROTECTED] wrote: On Nov 11, 11:57 am, Jaap Spies [EMAIL PROTECTED] wrote: John H Palmieri wrote: On Nov 11, 4:24 am, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here is 3.2.rc0 and I have to confess that I cheated: I did build this on numerous platforms before announcing here (if you hung out in IRC you knew about this release for about 6 hours now) and as it turns out my caution was justified. Doctesting is broken with this release unless you do the following: ./sage -sh cd local/bin hg update -C When I try to do the last line (on an intel mac running 10.5), I get this: abort: could not import module lookup! Did I do something wrong? do: ./sage -sh cd local/bin ./hg update -C Here's what happens: (/Applications/sage) [11:26am] ./sage -sh Starting subshell with Sage environment variables set. Be sure to exit when you are done and do not do anything with other copies of Sage! So far so good. (/Applications/sage) [11:58am] cd local/bin (...local/bin) [11:58am] ./hg update -C abort: could not import module lookup! mmh - can you try without the ./ since hg is in $PATH. I did that first, same problem. What shell are you using - even though this should not matter, but one never knows. Oh, this is the problem. I'm running tcsh (I got used to it years ago, and keep deciding it's too much work to switch). When I switch to bash, everything works. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
mabshoff wrote: Sources and a sage.math only binary can be found at http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ On Fedora 9, 32 bits the one and only failure: sage -t devel/sage/sage/combinat/root_system/weyl_characters.py*** *** Error: TIMED OUT! *** *** *** *** Error: TIMED OUT! *** *** [435.4 s] Surprising? Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.rc0 released
I got the same matrix_double_dense failure as J. Palmieri on intel macs running 10.4 and 10.5, plus this one which only occured on the 10.5 machine: sage -t devel/sage/sage/calculus/wester.py ** File /Users/mh/sagestuff/sage-3.2.rc0/devel/sage/sage/calculus/ wester.py, line 261: : [float(f(i/10)) for i in range(1,5)] Expected: BLANKLINE [-0.00033670040754082975, -0.0027778004096620235, -0.00989099409140..., -0.025411145508414...] Got: [-0.00033670040754081587, -0.0027778004096621622, -0.0098909940914039818, -0.025411145508414779] ** 1 items had failures: 1 of 193 in __main__.example_0 ***Test Failed*** 1 failures. -M. Hampton On Nov 11, 5:08 pm, Jaap Spies [EMAIL PROTECTED] wrote: mabshoff wrote: Sources and a sage.math only binary can be found at http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ On Fedora 9, 32 bits the one and only failure: sage -t devel/sage/sage/combinat/root_system/weyl_characters.py*** *** Error: TIMED OUT! *** *** *** *** Error: TIMED OUT! *** *** [435.4 s] Surprising? Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On Nov 7, 6:45 am, Justin C. Walker [EMAIL PROTECTED] wrote: On Nov 5, 2008, at 15:44 , mabshoff wrote: SNIP Mac OS X, 10.4.11 (Core 2 Duo): Built w/o problems All tests passed Mac OS X, 10.5.5 (Dual Quad Xeon): Built w/o problems. Testing (make -j2 test) gave 1 failure: sage -t devel/sage/sage/calculus/wester.py ** File /Users/tmp/sage-3.2.alpha3/tmp/wester.py, line 261: : [float(f(i/10)) for i in range(1,5)] Expected: BLANKLINE [-0.00033670040754082975, -0.0027778004096620235, -0.00989099409140..., -0.025411145508414...] Got: [-0.00033670040754081587, -0.0027778004096621622, -0.0098909940914039818, -0.025411145508414779] ** 1 items had failures: 1 of 193 in __main__.example_0 ***Test Failed*** 1 failures. For whitespace errors, see the file /Users/tmp/sage-3.2.alpha3/ tmp/.doctest_wester.py [9.2 s] Justin This is now #4472. Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
I just had one timeout failure on a PPC mac running 10.4, on modular/
abvar/homspace.py, plus the following malloc error which didn't cause
the test to fail but maybe its worth noting:
sage -t devel/sage/sage/libs/pari/gen.pyx
python(5728) malloc: *** vm_allocate(size=409600) failed (error
code=3)
python(5728) malloc: *** error: can't allocate region
python(5728) malloc: *** set a breakpoint in szone_error to debug
sage -t devel/sage/sage/modular/abvar/homspace.py *** ***
Error: TIMED OUT! *** ***
*** *** Error: TIMED OUT! *** ***
[443.8 s]
(Total time for all tests: 13549.5 seconds)
-Marshall
On Nov 6, 9:51 pm, mhampton [EMAIL PROTECTED] wrote:
All tests passed on my intel mac, running 10.4. I am building and
testing on a PPC 10.4 as well, but I won't be awake when that
finishes.
-Marshall
On Nov 6, 9:41 pm, Dan Drake [EMAIL PROTECTED] wrote:
On Thu, 06 Nov 2008 at 01:09PM -0500, David Joyner wrote:
[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]
I'm using Intrepid amd64 and get the same failures as Franco.
[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.
Here's what I get when I do that:
--
| Sage Version 3.2.alpha3, Release Date: 2008-11-05 |
| Type notebook() for the GUI, and license() for information.|
--
sage: lisp.eval('(* 4 5)')
'(* 4 5)\n20'
sage: lisp.eval('(+ 2 2)')
'(+ 2 2)\n4'
sage: lisp(0).bool()
True
As Georg said, it's some sporadic Lisp/Maxima thing that we're hoping is
fixed by switching to a different Lisp.
Dan
--
--- Dan Drake [EMAIL PROTECTED]
- KAIST Department of Mathematical Sciences
--- http://mathsci.kaist.ac.kr/~drake
signature.asc
1KViewDownload
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On Nov 7, 6:13 am, mhampton [EMAIL PROTECTED] wrote:
I just had one timeout failure on a PPC mac running 10.4, on modular/
abvar/homspace.py, plus the following malloc error which didn't cause
the test to fail but maybe its worth noting:
sage -t devel/sage/sage/libs/pari/gen.pyx
python(5728) malloc: *** vm_allocate(size=409600) failed (error
code=3)
python(5728) malloc: *** error: can't allocate region
python(5728) malloc: *** set a breakpoint in szone_error to debug
Yeah, the above is a known error (the printing of crap) and there
already is a ticket for it.
sage -t devel/sage/sage/modular/abvar/homspace.py *** ***
Error: TIMED OUT! *** ***
*** *** Error: TIMED OUT! *** ***
[443.8 s]
Please open a ticket for this so that we mark some tests as #long
time
(Total time for all tests: 13549.5 seconds)
-Marshall
Cheers,
Michael
On Nov 6, 9:51 pm, mhampton [EMAIL PROTECTED] wrote:
All tests passed on my intel mac, running 10.4. I am building and
testing on a PPC 10.4 as well, but I won't be awake when that
finishes.
-Marshall
On Nov 6, 9:41 pm, Dan Drake [EMAIL PROTECTED] wrote:
On Thu, 06 Nov 2008 at 01:09PM -0500, David Joyner wrote:
[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]
I'm using Intrepid amd64 and get the same failures as Franco.
[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.
Here's what I get when I do that:
--
| Sage Version 3.2.alpha3, Release Date: 2008-11-05 |
| Type notebook() for the GUI, and license() for information. |
--
sage: lisp.eval('(* 4 5)')
'(* 4 5)\n20'
sage: lisp.eval('(+ 2 2)')
'(+ 2 2)\n4'
sage: lisp(0).bool()
True
As Georg said, it's some sporadic Lisp/Maxima thing that we're hoping is
fixed by switching to a different Lisp.
Dan
--
--- Dan Drake [EMAIL PROTECTED]
- KAIST Department of Mathematical Sciences
--- http://mathsci.kaist.ac.kr/~drake
signature.asc
1KViewDownload
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On Nov 5, 2008, at 15:44 , mabshoff wrote: Hello folks, here goes 3.2.alpha3 - somewhat later than planned. Hopefully we fixed all numerical doctest noise from #788 (I even reverted a small number of changes) and otherwise merged a couple other nice patches. If this release builds and doctests fine it will likely become 3.2.final in the next 48 hours, otherwise there will be a 3.2.rc0. There is plenty of patches in trac to review, so those of you who have time please review some patches :) As usual sources and a sage.math binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Mac OS X, 10.4.11 (Core 2 Duo): Built w/o problems All tests passed Mac OS X, 10.5.5 (Dual Quad Xeon): Built w/o problems. Testing (make -j2 test) gave 1 failure: sage -t devel/sage/sage/calculus/wester.py ** File /Users/tmp/sage-3.2.alpha3/tmp/wester.py, line 261: : [float(f(i/10)) for i in range(1,5)] Expected: BLANKLINE [-0.00033670040754082975, -0.0027778004096620235, -0.00989099409140..., -0.025411145508414...] Got: [-0.00033670040754081587, -0.0027778004096621622, -0.0098909940914039818, -0.025411145508414779] ** 1 items had failures: 1 of 193 in __main__.example_0 ***Test Failed*** 1 failures. For whitespace errors, see the file /Users/tmp/sage-3.2.alpha3/ tmp/.doctest_wester.py [9.2 s] Justin -- Justin C. Walker, Curmudgeon-At-Large, Director Institute for the Enhancement of the Director's Income The path of least resistance: it's not just for electricity any more. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
OK, that's now #4463.
On Nov 7, 8:21 am, mabshoff [EMAIL PROTECTED] wrote:
On Nov 7, 6:13 am, mhampton [EMAIL PROTECTED] wrote:
I just had one timeout failure on a PPC mac running 10.4, on modular/
abvar/homspace.py, plus the following malloc error which didn't cause
the test to fail but maybe its worth noting:
sage -t devel/sage/sage/libs/pari/gen.pyx
python(5728) malloc: *** vm_allocate(size=409600) failed (error
code=3)
python(5728) malloc: *** error: can't allocate region
python(5728) malloc: *** set a breakpoint in szone_error to debug
Yeah, the above is a known error (the printing of crap) and there
already is a ticket for it.
sage -t devel/sage/sage/modular/abvar/homspace.py *** ***
Error: TIMED OUT! *** ***
*** *** Error: TIMED OUT! *** ***
[443.8 s]
Please open a ticket for this so that we mark some tests as #long
time
(Total time for all tests: 13549.5 seconds)
-Marshall
Cheers,
Michael
On Nov 6, 9:51 pm, mhampton [EMAIL PROTECTED] wrote:
All tests passed on my intel mac, running 10.4. I am building and
testing on a PPC 10.4 as well, but I won't be awake when that
finishes.
-Marshall
On Nov 6, 9:41 pm, Dan Drake [EMAIL PROTECTED] wrote:
On Thu, 06 Nov 2008 at 01:09PM -0500, David Joyner wrote:
[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]
I'm using Intrepid amd64 and get the same failures as Franco.
[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.
Here's what I get when I do that:
--
| Sage Version 3.2.alpha3, Release Date: 2008-11-05 |
| Type notebook() for the GUI, and license() for information.|
--
sage: lisp.eval('(* 4 5)')
'(* 4 5)\n20'
sage: lisp.eval('(+ 2 2)')
'(+ 2 2)\n4'
sage: lisp(0).bool()
True
As Georg said, it's some sporadic Lisp/Maxima thing that we're hoping is
fixed by switching to a different Lisp.
Dan
--
--- Dan Drake [EMAIL PROTECTED]
- KAIST Department of Mathematical Sciences
--- http://mathsci.kaist.ac.kr/~drake
signature.asc
1KViewDownload
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
With amd64 intrepid ibex, it builds fine but sage -testall seems to have the same locking-up issues as with the alpha2 version. I can ctrl c to get out of the doc files, and it will pass on to testing the next one, but when I ctrl-c at sage -t devel/sage/sage/libs/fplll/fplll.pyx it kicks me out of the test. I'm trying sage -testall --verbose now In const.tex (I think - maybe it's tut.tex?), it does this: Trying: f4 = lambda x:sin(Integer(2)*x)###line 734:_sage_: f4 = lambda x:sin(2*x) Expecting nothing ok Trying: f = Piecewise([[(Integer(0),Int locking-up in the middle of a line of type. (It often pauses very briefly in mid-line, so this is not an indication of a parsing problem, I'm guessing.) This time, sage -t devel/sage/sage/libs/fplll/fplll.pyx seems to have passed without problems but I'll post any other problems, if they arise. On Wed, Nov 5, 2008 at 6:44 PM, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here goes 3.2.alpha3 - somewhat later than planned. Hopefully we fixed all numerical doctest noise from #788 (I even reverted a small number of changes) and otherwise merged a couple other nice patches. If this release builds and doctests fine it will likely become 3.2.final in the next 48 hours, otherwise there will be a 3.2.rc0. There is plenty of patches in trac to review, so those of you who have time please review some patches :) As usual sources and a sage.math binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Cheers, Michael Merged in Sage 3.2.alpha3: #4035: Martin Albrecht: fix optional doctests for multivariate polynomials [Reviewed by Michael Abshoff] #4062: Craig Citro, Peter Bruin: Problems with Eisenstein series code [Reviewed by David Loeffler] #4388: John Cremona: elliptic curves: basis_matrix command totally broken [Reviewed by David Loeffler] #4406: Robert Bradshaw: make polynomial truncation cpdef method [Reviewed by Michael Abshoff] #4415: Nicolas Thiery: update sage-combinat script to latest upstream version [Reviewed by Michael Abshoff] #4416: Michael Abshoff: Sage 3.2.a2: optional doctest failure in sage/ rings/arith.py [Reviewed by Craig Citro] #4417: John Palmieri: fix steenrod algebra 'optional' doctest [Reviewed by Michael Abshoff] #4418: Minh Nguyen: typos in files under crypto/mq [Reviewed by Michael Abshoff] #4420: Martin Albrecht: sort Gröbner bases [Reviewed by Michael Abshoff] #4423: John Palmieri: document branch cut for Ei [Reviewed by Martin Albrecht] #4427: Martin Albrecht: use RTLD symbols instead of constants in init_singular [Reviewed by Michael Abshoff] #4428: Craig Citro: Forgot to close open files in sage/rings/ number_field/totallyreal_phc.py [Reviewed by Michael Abshoff] #4434: William Stein: hgmerge massively broken on os x [Reviewed by Michael Abshoff] #4436: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/ calculus.py [Reviewed by Mike Hansen] #4437: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/graphs/ graph.py [Reviewed by Mike Hansen] #4438: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/ functional.py and wester.py [Reviewed by Craig Citro] #4439: Michael Abshoff: Sage 3.2.a2: make three doctests from #788 random again [Reviewed by Craig Citro] #4441: Goerg Weber: remove two obsolete entries from modabvar documentation [Reviewed by Michael Abshoff] #4442: Goerg Weber: fix documetation build issue with congroup.py [Reviewed by Michael Abshoff] #4445: Robert Miller: is_isomorphic throws an error when the graph is compared to itself [Reviewed by Jason Grout] #4449: Franco Soliola: sage-combinat install script doesn't work with 3.2.alpha2 [Reviewed by Michael Abshoff] --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On my laptop which normally builds Sage fine I get this (at the end of install.log): sage-3.2.alpha3/.hg/store/data/sagebuild.py.i sage-3.2.alpha3/.hg/store/data/setup.py.d sage-3.2.alpha3/.hg/store/data/setup.py.i sage-3.2.alpha3/.hg/store/data/setupnb.py.i sage-3.2.alpha3/.hg/store/data/spkg-debian-maybe.i sage-3.2.alpha3/.hg/store/data/spkg-delauto.i sage-3.2.alpha3/.hg/store/data/spkg-dist.i sage-3.2.alpha3/.hg/store/data/spkg-install.i sage-3.2.alpha3/.hg/store/data/test__changed.i sage-3.2.alpha3/.hg/store/00changelog.d sage-3.2.alpha3/.hg/store/00changelog.i sage-3.2.alpha3/.hg/store/00manifest.d Finished extraction There is no spkg-install script, no setup.py, and no configure script, so I do not know how to install /home/john/sage-3.2.alpha3/spkg/standard/sage-3.2.alpha3.spkg. make[1]: *** [installed/sage-3.2.alpha3] Error 1 make[1]: Leaving directory `/home/john/sage-3.2.alpha3/spkg' Command exited with non-zero status 2 3279.30user 371.66system 1:02:22elapsed 97%CPU (0avgtext+0avgdata 0maxresident)k 248752inputs+7397400outputs (1382major+120951920minor)pagefaults 0swaps What's up? John 2008/11/5 mabshoff [EMAIL PROTECTED]: Hello folks, here goes 3.2.alpha3 - somewhat later than planned. Hopefully we fixed all numerical doctest noise from #788 (I even reverted a small number of changes) and otherwise merged a couple other nice patches. If this release builds and doctests fine it will likely become 3.2.final in the next 48 hours, otherwise there will be a 3.2.rc0. There is plenty of patches in trac to review, so those of you who have time please review some patches :) As usual sources and a sage.math binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Cheers, Michael Merged in Sage 3.2.alpha3: #4035: Martin Albrecht: fix optional doctests for multivariate polynomials [Reviewed by Michael Abshoff] #4062: Craig Citro, Peter Bruin: Problems with Eisenstein series code [Reviewed by David Loeffler] #4388: John Cremona: elliptic curves: basis_matrix command totally broken [Reviewed by David Loeffler] #4406: Robert Bradshaw: make polynomial truncation cpdef method [Reviewed by Michael Abshoff] #4415: Nicolas Thiery: update sage-combinat script to latest upstream version [Reviewed by Michael Abshoff] #4416: Michael Abshoff: Sage 3.2.a2: optional doctest failure in sage/ rings/arith.py [Reviewed by Craig Citro] #4417: John Palmieri: fix steenrod algebra 'optional' doctest [Reviewed by Michael Abshoff] #4418: Minh Nguyen: typos in files under crypto/mq [Reviewed by Michael Abshoff] #4420: Martin Albrecht: sort Gröbner bases [Reviewed by Michael Abshoff] #4423: John Palmieri: document branch cut for Ei [Reviewed by Martin Albrecht] #4427: Martin Albrecht: use RTLD symbols instead of constants in init_singular [Reviewed by Michael Abshoff] #4428: Craig Citro: Forgot to close open files in sage/rings/ number_field/totallyreal_phc.py [Reviewed by Michael Abshoff] #4434: William Stein: hgmerge massively broken on os x [Reviewed by Michael Abshoff] #4436: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/ calculus.py [Reviewed by Mike Hansen] #4437: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/graphs/ graph.py [Reviewed by Mike Hansen] #4438: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/ functional.py and wester.py [Reviewed by Craig Citro] #4439: Michael Abshoff: Sage 3.2.a2: make three doctests from #788 random again [Reviewed by Craig Citro] #4441: Goerg Weber: remove two obsolete entries from modabvar documentation [Reviewed by Michael Abshoff] #4442: Goerg Weber: fix documetation build issue with congroup.py [Reviewed by Michael Abshoff] #4445: Robert Miller: is_isomorphic throws an error when the graph is compared to itself [Reviewed by Jason Grout] #4449: Franco Soliola: sage-combinat install script doesn't work with 3.2.alpha2 [Reviewed by Michael Abshoff] --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On Thu, Nov 6, 2008 at 7:51 AM, 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 can ctrl c to get out of the doc files, and it will pass on to testing
the next one, but when I ctrl-c at
sage -t devel/sage/sage/libs/fplll/fplll.pyx
it kicks me out of the test.
I'm trying sage -testall --verbose now
In const.tex (I think - maybe it's tut.tex?), it does this:
Trying:
f4 = lambda x:sin(Integer(2)*x)###line 734:_sage_: f4 = lambda
x:sin(2*x)
Expecting nothing
ok
Trying:
f = Piecewise([[(Integer(0),Int
locking-up in the middle of a line of type. (It often pauses very briefly
in mid-line, so this is not an indication of a parsing problem, I'm guessing.)
This time, sage -t devel/sage/sage/libs/fplll/fplll.pyx seems to have
passed without problems but I'll post any other problems, if they arise.
Now it is locked at
sage -t --verbose devel/sage/sage/libs/pari/gen_py.py
at the line
Trying:
a = pari('(3+I)/2').python(); a###line 98:_sage_ a =
pari('(3+I)/2').python(); a
On Wed, Nov 5, 2008 at 6:44 PM, mabshoff [EMAIL PROTECTED] wrote:
Hello folks,
here goes 3.2.alpha3 - somewhat later than planned. Hopefully we
fixed all numerical doctest noise from #788 (I even reverted a small
number of changes) and otherwise merged a couple other nice patches.
If this release builds and doctests fine it will likely become
3.2.final in the next 48 hours, otherwise there will be a 3.2.rc0.
There is plenty of patches in trac to review, so those of you who have
time please review some patches :)
As usual sources and a sage.math binary is in
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/
Cheers,
Michael
Merged in Sage 3.2.alpha3:
#4035: Martin Albrecht: fix optional doctests for multivariate
polynomials [Reviewed by Michael Abshoff]
#4062: Craig Citro, Peter Bruin: Problems with Eisenstein series code
[Reviewed by David Loeffler]
#4388: John Cremona: elliptic curves: basis_matrix command totally
broken [Reviewed by David Loeffler]
#4406: Robert Bradshaw: make polynomial truncation cpdef method
[Reviewed by Michael Abshoff]
#4415: Nicolas Thiery: update sage-combinat script to latest upstream
version [Reviewed by Michael Abshoff]
#4416: Michael Abshoff: Sage 3.2.a2: optional doctest failure in sage/
rings/arith.py [Reviewed by Craig Citro]
#4417: John Palmieri: fix steenrod algebra 'optional' doctest
[Reviewed by Michael Abshoff]
#4418: Minh Nguyen: typos in files under crypto/mq [Reviewed by
Michael Abshoff]
#4420: Martin Albrecht: sort Gröbner bases [Reviewed by Michael
Abshoff]
#4423: John Palmieri: document branch cut for Ei [Reviewed by Martin
Albrecht]
#4427: Martin Albrecht: use RTLD symbols instead of constants in
init_singular [Reviewed by Michael Abshoff]
#4428: Craig Citro: Forgot to close open files in sage/rings/
number_field/totallyreal_phc.py [Reviewed by Michael Abshoff]
#4434: William Stein: hgmerge massively broken on os x [Reviewed by
Michael Abshoff]
#4436: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/
calculus.py [Reviewed by Mike Hansen]
#4437: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/graphs/
graph.py [Reviewed by Mike Hansen]
#4438: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/
functional.py and wester.py [Reviewed by Craig Citro]
#4439: Michael Abshoff: Sage 3.2.a2: make three doctests from #788
random again [Reviewed by Craig Citro]
#4441: Goerg Weber: remove two obsolete entries from modabvar
documentation [Reviewed by Michael Abshoff]
#4442: Goerg Weber: fix documetation build issue with congroup.py
[Reviewed by Michael Abshoff]
#4445: Robert Miller: is_isomorphic throws an error when the graph is
compared to itself [Reviewed by Jason Grout]
#4449: Franco Soliola: sage-combinat install script doesn't work with
3.2.alpha2 [Reviewed by Michael Abshoff]
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On Wed, Nov 5, 2008 at 3:44 PM, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here goes 3.2.alpha3 - somewhat later than planned. Hopefully we fixed all numerical doctest noise from #788 (I even reverted a small number of changes) and otherwise merged a couple other nice patches. On OS X 10.5.x 32-bit intel there is one numerical noise issue: sage -t devel/sage/sage/calculus/wester.py ** File /Users/was/build/sage-3.2.alpha3/tmp/wester.py, line 261: : [float(f(i/10)) for i in range(1,5)] Expected: BLANKLINE [-0.00033670040754082975, -0.0027778004096620235, -0.00989099409140..., -0.025411145508414...] Got: [-0.00033670040754081587, -0.0027778004096621622, -0.0098909940914039818, -0.025411145508414779] ** 1 items had failures: 1 of 193 in __main__.example_0 ***Test Failed*** 1 failures. For whitespace errors, see the file /Users/was/build/sage-3.2.alpha3/tmp/.doctest_wester.py [11.4 s] If this release builds and doctests fine it will likely become 3.2.final in the next 48 hours, otherwise there will be a 3.2.rc0. There is plenty of patches in trac to review, so those of you who have time please review some patches :) As usual sources and a sage.math binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Cheers, Michael Merged in Sage 3.2.alpha3: #4035: Martin Albrecht: fix optional doctests for multivariate polynomials [Reviewed by Michael Abshoff] #4062: Craig Citro, Peter Bruin: Problems with Eisenstein series code [Reviewed by David Loeffler] #4388: John Cremona: elliptic curves: basis_matrix command totally broken [Reviewed by David Loeffler] #4406: Robert Bradshaw: make polynomial truncation cpdef method [Reviewed by Michael Abshoff] #4415: Nicolas Thiery: update sage-combinat script to latest upstream version [Reviewed by Michael Abshoff] #4416: Michael Abshoff: Sage 3.2.a2: optional doctest failure in sage/ rings/arith.py [Reviewed by Craig Citro] #4417: John Palmieri: fix steenrod algebra 'optional' doctest [Reviewed by Michael Abshoff] #4418: Minh Nguyen: typos in files under crypto/mq [Reviewed by Michael Abshoff] #4420: Martin Albrecht: sort Gröbner bases [Reviewed by Michael Abshoff] #4423: John Palmieri: document branch cut for Ei [Reviewed by Martin Albrecht] #4427: Martin Albrecht: use RTLD symbols instead of constants in init_singular [Reviewed by Michael Abshoff] #4428: Craig Citro: Forgot to close open files in sage/rings/ number_field/totallyreal_phc.py [Reviewed by Michael Abshoff] #4434: William Stein: hgmerge massively broken on os x [Reviewed by Michael Abshoff] #4436: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/ calculus.py [Reviewed by Mike Hansen] #4437: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/graphs/ graph.py [Reviewed by Mike Hansen] #4438: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/ functional.py and wester.py [Reviewed by Craig Citro] #4439: Michael Abshoff: Sage 3.2.a2: make three doctests from #788 random again [Reviewed by Craig Citro] #4441: Goerg Weber: remove two obsolete entries from modabvar documentation [Reviewed by Michael Abshoff] #4442: Goerg Weber: fix documetation build issue with congroup.py [Reviewed by Michael Abshoff] #4445: Robert Miller: is_isomorphic throws an error when the graph is compared to itself [Reviewed by Jason Grout] #4449: Franco Soliola: sage-combinat install script doesn't work with 3.2.alpha2 [Reviewed by Michael Abshoff] -- 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
Hi, on Core2 Duo Intel OS X 10.4.11 (Xcdoe 2.5) Sage.3.2.alpha3 builds fine. I immediately ran MAKE testlong, and it only gives the two long known failures (trac tickets in the 3xxx range): -- The following tests failed: sage -t -long devel/sage/sage/crypto/mq/sr.py sage -t -long devel/sage/sage/schemes/elliptic_curves/ ell_finite_field.py Total time for all tests: 8987.8 seconds Cheers, gsw --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On Debian stable 32-bit one test fails:
sage -t devel/sage/sage/interfaces/r.py
**
File /local/data/huss/software/sage-3.2.alpha3/tmp/r.py, line 549:
sage: r.library('foobar')
Expected:
Traceback (most recent call last):
...
ImportError: there is no package called 'foobar'
Got nothing
**
File /local/data/huss/software/sage-3.2.alpha3/tmp/r.py, line 850:
sage: r.completions('tes')
Expected:
['testPlatformEquivalence', 'testVirtual']
Got:
['testPlatformEquivalence', 'testPlatformEquivalence',
'testVirtual', 'testVirtual']
**
On 6 Nov., 00:44, mabshoff [EMAIL PROTECTED] wrote:
Hello folks,
here goes 3.2.alpha3 - somewhat later than planned. Hopefully we
fixed all numerical doctest noise from #788 (I even reverted a small
number of changes) and otherwise merged a couple other nice patches.
If this release builds and doctests fine it will likely become
3.2.final in the next 48 hours, otherwise there will be a 3.2.rc0.
There is plenty of patches in trac to review, so those of you who have
time please review some patches :)
As usual sources and a sage.math binary is in
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/
Cheers,
Michael
Merged in Sage 3.2.alpha3:
#4035: Martin Albrecht: fix optional doctests for multivariate
polynomials [Reviewed by Michael Abshoff]
#4062: Craig Citro, Peter Bruin: Problems with Eisenstein series code
[Reviewed by David Loeffler]
#4388: John Cremona: elliptic curves: basis_matrix command totally
broken [Reviewed by David Loeffler]
#4406: Robert Bradshaw: make polynomial truncation cpdef method
[Reviewed by Michael Abshoff]
#4415: Nicolas Thiery: update sage-combinat script to latest upstream
version [Reviewed by Michael Abshoff]
#4416: Michael Abshoff: Sage 3.2.a2: optional doctest failure in sage/
rings/arith.py [Reviewed by Craig Citro]
#4417: John Palmieri: fix steenrod algebra 'optional' doctest
[Reviewed by Michael Abshoff]
#4418: Minh Nguyen: typos in files under crypto/mq [Reviewed by
Michael Abshoff]
#4420: Martin Albrecht: sort Gröbner bases [Reviewed by Michael
Abshoff]
#4423: John Palmieri: document branch cut for Ei [Reviewed by Martin
Albrecht]
#4427: Martin Albrecht: use RTLD symbols instead of constants in
init_singular [Reviewed by Michael Abshoff]
#4428: Craig Citro: Forgot to close open files in sage/rings/
number_field/totallyreal_phc.py [Reviewed by Michael Abshoff]
#4434: William Stein: hgmerge massively broken on os x [Reviewed by
Michael Abshoff]
#4436: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/
calculus.py [Reviewed by Mike Hansen]
#4437: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/graphs/
graph.py [Reviewed by Mike Hansen]
#4438: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/
functional.py and wester.py [Reviewed by Craig Citro]
#4439: Michael Abshoff: Sage 3.2.a2: make three doctests from #788
random again [Reviewed by Craig Citro]
#4441: Goerg Weber: remove two obsolete entries from modabvar
documentation [Reviewed by Michael Abshoff]
#4442: Goerg Weber: fix documetation build issue with congroup.py
[Reviewed by Michael Abshoff]
#4445: Robert Miller: is_isomorphic throws an error when the graph is
compared to itself [Reviewed by Jason Grout]
#4449: Franco Soliola: sage-combinat install script doesn't work with
3.2.alpha2 [Reviewed by Michael Abshoff]
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
Build ok and all tests pass on here (32-bit linux):
Linux version 2.6.16.60-0.31-smp ([EMAIL PROTECTED]) (gcc version 4.1.2
20070115 (SUSE Linux)) #1 SMP Tue Oct 7 16:16:29 UTC 2008
and here (64-bit linux):
Linux version 2.6.24-19-generic ([EMAIL PROTECTED]) (gcc version 4.2.3
(Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:15:37 UTC 2008
John
2008/11/6 Wilfried_Huss [EMAIL PROTECTED]:
On Debian stable 32-bit one test fails:
sage -t devel/sage/sage/interfaces/r.py
**
File /local/data/huss/software/sage-3.2.alpha3/tmp/r.py, line 549:
sage: r.library('foobar')
Expected:
Traceback (most recent call last):
...
ImportError: there is no package called 'foobar'
Got nothing
**
File /local/data/huss/software/sage-3.2.alpha3/tmp/r.py, line 850:
sage: r.completions('tes')
Expected:
['testPlatformEquivalence', 'testVirtual']
Got:
['testPlatformEquivalence', 'testPlatformEquivalence',
'testVirtual', 'testVirtual']
**
On 6 Nov., 00:44, mabshoff [EMAIL PROTECTED] wrote:
Hello folks,
here goes 3.2.alpha3 - somewhat later than planned. Hopefully we
fixed all numerical doctest noise from #788 (I even reverted a small
number of changes) and otherwise merged a couple other nice patches.
If this release builds and doctests fine it will likely become
3.2.final in the next 48 hours, otherwise there will be a 3.2.rc0.
There is plenty of patches in trac to review, so those of you who have
time please review some patches :)
As usual sources and a sage.math binary is in
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/
Cheers,
Michael
Merged in Sage 3.2.alpha3:
#4035: Martin Albrecht: fix optional doctests for multivariate
polynomials [Reviewed by Michael Abshoff]
#4062: Craig Citro, Peter Bruin: Problems with Eisenstein series code
[Reviewed by David Loeffler]
#4388: John Cremona: elliptic curves: basis_matrix command totally
broken [Reviewed by David Loeffler]
#4406: Robert Bradshaw: make polynomial truncation cpdef method
[Reviewed by Michael Abshoff]
#4415: Nicolas Thiery: update sage-combinat script to latest upstream
version [Reviewed by Michael Abshoff]
#4416: Michael Abshoff: Sage 3.2.a2: optional doctest failure in sage/
rings/arith.py [Reviewed by Craig Citro]
#4417: John Palmieri: fix steenrod algebra 'optional' doctest
[Reviewed by Michael Abshoff]
#4418: Minh Nguyen: typos in files under crypto/mq [Reviewed by
Michael Abshoff]
#4420: Martin Albrecht: sort Gröbner bases [Reviewed by Michael
Abshoff]
#4423: John Palmieri: document branch cut for Ei [Reviewed by Martin
Albrecht]
#4427: Martin Albrecht: use RTLD symbols instead of constants in
init_singular [Reviewed by Michael Abshoff]
#4428: Craig Citro: Forgot to close open files in sage/rings/
number_field/totallyreal_phc.py [Reviewed by Michael Abshoff]
#4434: William Stein: hgmerge massively broken on os x [Reviewed by
Michael Abshoff]
#4436: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/
calculus.py [Reviewed by Mike Hansen]
#4437: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/graphs/
graph.py [Reviewed by Mike Hansen]
#4438: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/
functional.py and wester.py [Reviewed by Craig Citro]
#4439: Michael Abshoff: Sage 3.2.a2: make three doctests from #788
random again [Reviewed by Craig Citro]
#4441: Goerg Weber: remove two obsolete entries from modabvar
documentation [Reviewed by Michael Abshoff]
#4442: Goerg Weber: fix documetation build issue with congroup.py
[Reviewed by Michael Abshoff]
#4445: Robert Miller: is_isomorphic throws an error when the graph is
compared to itself [Reviewed by Jason Grout]
#4449: Franco Soliola: sage-combinat install script doesn't work with
3.2.alpha2 [Reviewed by Michael Abshoff]
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
mabshoff wrote: Hello folks, here goes 3.2.alpha3 - somewhat later than planned. Hopefully we fixed all numerical doctest noise from #788 (I even reverted a small number of changes) and otherwise merged a couple other nice patches. If this release builds and doctests fine it will likely become 3.2.final in the next 48 hours, otherwise there will be a 3.2.rc0. There is plenty of patches in trac to review, so those of you who have time please review some patches :) As usual sources and a sage.math binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ On Fedora 9, 32 bits: -- The following tests failed: sage -t devel/sage/sage/combinat/root_system/weyl_characters.py But this seems to be a time out problem. sage -t devel/sage/sage/combinat/root_system/weyl_characters.py [256.5 s] -- All tests passed! Total time for all tests: 256.5 seconds Jaap --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
Whatever caused that I don't know, but I started again from a fresh download and all was fine. Sorry for the noise. 2008/11/6 John Cremona [EMAIL PROTECTED]: On my laptop which normally builds Sage fine I get this (at the end of install.log): sage-3.2.alpha3/.hg/store/data/sagebuild.py.i sage-3.2.alpha3/.hg/store/data/setup.py.d sage-3.2.alpha3/.hg/store/data/setup.py.i sage-3.2.alpha3/.hg/store/data/setupnb.py.i sage-3.2.alpha3/.hg/store/data/spkg-debian-maybe.i sage-3.2.alpha3/.hg/store/data/spkg-delauto.i sage-3.2.alpha3/.hg/store/data/spkg-dist.i sage-3.2.alpha3/.hg/store/data/spkg-install.i sage-3.2.alpha3/.hg/store/data/test__changed.i sage-3.2.alpha3/.hg/store/00changelog.d sage-3.2.alpha3/.hg/store/00changelog.i sage-3.2.alpha3/.hg/store/00manifest.d Finished extraction There is no spkg-install script, no setup.py, and no configure script, so I do not know how to install /home/john/sage-3.2.alpha3/spkg/standard/sage-3.2.alpha3.spkg. make[1]: *** [installed/sage-3.2.alpha3] Error 1 make[1]: Leaving directory `/home/john/sage-3.2.alpha3/spkg' Command exited with non-zero status 2 3279.30user 371.66system 1:02:22elapsed 97%CPU (0avgtext+0avgdata 0maxresident)k 248752inputs+7397400outputs (1382major+120951920minor)pagefaults 0swaps What's up? John 2008/11/5 mabshoff [EMAIL PROTECTED]: Hello folks, here goes 3.2.alpha3 - somewhat later than planned. Hopefully we fixed all numerical doctest noise from #788 (I even reverted a small number of changes) and otherwise merged a couple other nice patches. If this release builds and doctests fine it will likely become 3.2.final in the next 48 hours, otherwise there will be a 3.2.rc0. There is plenty of patches in trac to review, so those of you who have time please review some patches :) As usual sources and a sage.math binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/ Cheers, Michael Merged in Sage 3.2.alpha3: #4035: Martin Albrecht: fix optional doctests for multivariate polynomials [Reviewed by Michael Abshoff] #4062: Craig Citro, Peter Bruin: Problems with Eisenstein series code [Reviewed by David Loeffler] #4388: John Cremona: elliptic curves: basis_matrix command totally broken [Reviewed by David Loeffler] #4406: Robert Bradshaw: make polynomial truncation cpdef method [Reviewed by Michael Abshoff] #4415: Nicolas Thiery: update sage-combinat script to latest upstream version [Reviewed by Michael Abshoff] #4416: Michael Abshoff: Sage 3.2.a2: optional doctest failure in sage/ rings/arith.py [Reviewed by Craig Citro] #4417: John Palmieri: fix steenrod algebra 'optional' doctest [Reviewed by Michael Abshoff] #4418: Minh Nguyen: typos in files under crypto/mq [Reviewed by Michael Abshoff] #4420: Martin Albrecht: sort Gröbner bases [Reviewed by Michael Abshoff] #4423: John Palmieri: document branch cut for Ei [Reviewed by Martin Albrecht] #4427: Martin Albrecht: use RTLD symbols instead of constants in init_singular [Reviewed by Michael Abshoff] #4428: Craig Citro: Forgot to close open files in sage/rings/ number_field/totallyreal_phc.py [Reviewed by Michael Abshoff] #4434: William Stein: hgmerge massively broken on os x [Reviewed by Michael Abshoff] #4436: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/ calculus.py [Reviewed by Mike Hansen] #4437: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/graphs/ graph.py [Reviewed by Mike Hansen] #4438: Michael Abshoff: Sage 3.2.a2: numerical noise in sage/calculus/ functional.py and wester.py [Reviewed by Craig Citro] #4439: Michael Abshoff: Sage 3.2.a2: make three doctests from #788 random again [Reviewed by Craig Citro] #4441: Goerg Weber: remove two obsolete entries from modabvar documentation [Reviewed by Michael Abshoff] #4442: Goerg Weber: fix documetation build issue with congroup.py [Reviewed by Michael Abshoff] #4445: Robert Miller: is_isomorphic throws an error when the graph is compared to itself [Reviewed by Jason Grout] #4449: Franco Soliola: sage-combinat install script doesn't work with 3.2.alpha2 [Reviewed by Michael Abshoff] --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
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?
Also check from within Sage, since I am getting the same failures
there.
sage -t devel/sage/sage/interfaces/lisp.py
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 5:
sage: lisp.eval('(* 4 5)')
Expected:
'20'
Got:
'(* 4 5)\n20'
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 22:
sage: lisp.eval('(+ %s %s)'%(a.name(), b.name()))
Expected:
'8'
Got:
'(+ sage0 sage1)\n8'
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 27:
sage: lisp.eval('(defun factorial (n) (if (= n 1) 1 (* n
(factorial (- n 1)')
Expected:
'FACTORIAL'
Got:
'(defun factorial (n) (if (= n 1) 1 (* n (factorial (- n 1)\nFACTORIAL'
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 109:
sage: lisp.eval('(+ 2 2)')
Expected:
'4'
Got:
'(+ 2 2)\n4'
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 393:
sage: one == one
Expected:
True
Got:
False
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 397:
sage: one two
Expected:
True
Got:
False
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 403:
sage: two == 2
Expected:
True
Got:
False
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 423:
sage: lisp(0).bool()
Expected:
False
Got:
True
**
4 items had failures:
3 of 17 in __main__.example_0
1 of 3 in __main__.example_2
3 of 9 in __main__.example_24
1 of 5 in __main__.example_25
***Test Failed*** 8 failures.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
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.
Also check from within Sage, since I am getting the same failures
there.
sage -t devel/sage/sage/interfaces/lisp.py
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 5:
sage: lisp.eval('(* 4 5)')
Expected:
'20'
Got:
'(* 4 5)\n20'
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 22:
sage: lisp.eval('(+ %s %s)'%(a.name(), b.name()))
Expected:
'8'
Got:
'(+ sage0 sage1)\n8'
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 27:
sage: lisp.eval('(defun factorial (n) (if (= n 1) 1 (* n
(factorial (- n 1)')
Expected:
'FACTORIAL'
Got:
'(defun factorial (n) (if (= n 1) 1 (* n (factorial (- n 1)\nFACTORIAL'
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 109:
sage: lisp.eval('(+ 2 2)')
Expected:
'4'
Got:
'(+ 2 2)\n4'
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 393:
sage: one == one
Expected:
True
Got:
False
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 397:
sage: one two
Expected:
True
Got:
False
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 403:
sage: two == 2
Expected:
True
Got:
False
**
File /home/saliola/Applications/sage-3.2.alpha3/tmp/lisp.py, line 423:
sage: lisp(0).bool()
Expected:
False
Got:
True
**
4 items had failures:
3 of 17 in __main__.example_0
1 of 3 in __main__.example_2
3 of 9 in __main__.example_24
1 of 5 in __main__.example_25
***Test Failed*** 8 failures.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
Hi David, hi Franco, currently Sage has a known weakness with the Maxima synchronization resp. the lisp processes that are started by Maxima, which hits only sporadically and seems to be related to dynamical memory allocation done deep in the bowels of the lisp implementation. It has never been really tracked down so far, but maybe Intrepid Ibex brings some gcc compiler version / glibc version / malloc version / linux kernel / whatsoever that triggers the problematic behaviour more often than in the past. Of course, this is wild guessing ... Michael had hoped that this would go away by switching to another lisp package, but I don't know what the state of matters is. I can also trigger this (or some completely different?) sporadic problem on my bronze-age 768 MByte 550 MHz PPC Mac PowerBook, but even building Sage takes more than half a day. I'll give Sage3.2.alpha3 a try there. Cheers, gsw --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On Thu, Nov 6, 2008 at 11:03 AM, Franco Saliola [EMAIL PROTECTED] wrote: 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. That's because there is no other code that relies on lisp.py. The only functionality that relies on lisp.py is the %lisp mode in the notebook. -- William --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
2008/11/6 John Cremona [EMAIL PROTECTED]: Whatever caused that I don't know, but I started again from a fresh download and all was fine. Sorry for the noise. -testall -long: all passed --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On Nov 6, 12:42 pm, John Cremona [EMAIL PROTECTED] wrote: 2008/11/6 John Cremona [EMAIL PROTECTED]: Whatever caused that I don't know, but I started again from a fresh download and all was fine. Sorry for the noise. -testall -long: all passed Hi John, I would have guess corruption and since the new tarball worked I guess that was it. Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.alpha3 released
On Nov 6, 6:11 am, William Stein [EMAIL PROTECTED] wrote: On Wed, Nov 5, 2008 at 3:44 PM, mabshoff [EMAIL PROTECTED] wrote: Hello folks, here goes 3.2.alpha3 - somewhat later than planned. Hopefully we fixed all numerical doctest noise from #788 (I even reverted a small number of changes) and otherwise merged a couple other nice patches. On OS X 10.5.x 32-bit intel there is one numerical noise issue: sage -t devel/sage/sage/calculus/wester.py ** File /Users/was/build/sage-3.2.alpha3/tmp/wester.py, line 261: : [float(f(i/10)) for i in range(1,5)] Expected: BLANKLINE [-0.00033670040754082975, -0.0027778004096620235, -0.00989099409140..., -0.025411145508414...] Got: [-0.00033670040754081587, -0.0027778004096621622, -0.0098909940914039818, -0.025411145508414779] ** 1 items had failures: 1 of 193 in __main__.example_0 ***Test Failed*** 1 failures. For whitespace errors, see the file /Users/was/build/sage-3.2.alpha3/tmp/.doctest_wester.py [11.4 s] Is there a ticket yet? Did you run the tests on the build farm or is there coming more? Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
