[sage-devel] Re: Sage 3.0.6.alpha0 released
I was able to reproduce this on many different machines, all had only one common case - they had GCC 4.3.1 or later - additional to my system there is also friends Debian that is affected, as of arch a way to make it reproducible is to update to latest (pacman -Syu) still looking for someone with GCC 4.3.0 to see if those are all gcc 4.3.x or only 4.3.1 (this happens on different cpus, happened on amd barton, semptron and intel core 2 duo, also on different glibc versions, gcc seems to be only connecting element as far as I found out, in all cases adding those two flags to Make-arch fixes it... I will look into gcc bugtracker, maybe there is something to explain it) cheers, Andrzej. gcc -v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.1-6' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.3.1 (Debian 4.3.1-6) --~--~-~--~~~---~--~~ 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.0.6.alpha0 released
Hi, after some sniffing around, I noticed that for me (see bottom of mail for gcc version) techyon needs to be compiled with make linux (with disabled threads) or with -fno-crossjumping -fno-reorder-blocks added to Make-arch file at line 1134 (linux-thr target, after -O6) - second is better solution I think... both solutions fixes segfault, I don't know where the problem is, it can be gcc bug so special case for it might need to be added, does anyone have same gcc to verify that's it's gccs fault or not? cheers, Andrzej. [EMAIL PROTECTED] ~]$ gcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../configure --prefix=/usr --enable-shared --enable-languages=c,c++,fortran,objc,obj-c++,treelang --enable-threads=posix --mandir=/usr/share/man --enable-__cxa_atexit --disable-multilib --libdir=/usr/lib --libexecdir=/usr/lib --enable-clocale=gnu --disable-libstdcxx-pch --with-tune=generic Thread model: posix gcc version 4.3.1 20080626 (prerelease) (GCC) --~--~-~--~~~---~--~~ 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.0.6.alpha0 released
Hi, some new informations, gcc 4.2.4 is also affected by this, but all gcc = 4.2.3 are for sure working right, for 4.2.4 and 4.3.1 tachyon segfaults, I'm looking for some live cd with gcc 4.3 to see if problem is also visible in it or not, it seems to appear in gcc trunk somewhere between 2008-02-01(release of 4.2.3, works) and 2008-05-19 (release of 4.2.4, do not work - this really makes me think it is bug in gcc, minor releases should break optimizer I think, it only happened with major versions in past) - 4.3 was exactly between those two dates so it can narrow search a lot to somewhere in 2008-02-01 and 2008-03-05 or 2008-03-05 and 2008-05-19, also trying to see if it can be reproduced with some small code-only test case... should this become trac ticket? If yes I probably will be able to create one I think... cheers, Andrzej. --~--~-~--~~~---~--~~ 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.0.6.alpha0 released
On Jul 21, 1:35 pm, Andrzej Giniewicz [EMAIL PROTECTED] wrote: Hi, Hi Andrzej, some new informations, gcc 4.2.4 is also affected by this, but all gcc = 4.2.3 are for sure working right, for 4.2.4 and 4.3.1 tachyon segfaults, I'm looking for some live cd with gcc 4.3 to see if problem is also visible in it or not, it seems to appear in gcc trunk somewhere between 2008-02-01(release of 4.2.3, works) and 2008-05-19 (release of 4.2.4, do not work - this really makes me think it is bug in gcc, minor releases should break optimizer I think, it only happened with major versions in past) - 4.3 was exactly between those two dates so it can narrow search a lot to somewhere in 2008-02-01 and 2008-03-05 or 2008-03-05 and 2008-05-19, also trying to see if it can be reproduced with some small code-only test case... Really nice work. should this become trac ticket? If yes I probably will be able to create one I think... Yes and also check with the upstream author if he already knows about the issue. cheers, Andrzej. 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.0.6.alpha0 released
On Jul 19, 10:01 am, Andrzej Giniewicz [EMAIL PROTECTED] wrote: Hi, after some sniffing around, I noticed that for me (see bottom of mail for gcc version) techyon needs to be compiled with make linux (with disabled threads) or with -fno-crossjumping -fno-reorder-blocks added to Make-arch file at line 1134 (linux-thr target, after -O6) - Hi, can you dial that down to -O3 and if that fails to -O2? I do not believe that -O6 does anything beyond -O3, but I am too lazy to look it up now. Either way, -O6 is likely counterproductive. second is better solution I think... both solutions fixes segfault, I don't know where the problem is, it can be gcc bug so special case for it might need to be added, does anyone have same gcc to verify that's it's gccs fault or not? cheers, Andrzej. [EMAIL PROTECTED] ~]$ gcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../configure --prefix=/usr --enable-shared --enable-languages=c,c++,fortran,objc,obj-c++,treelang --enable-threads=posix --mandir=/usr/share/man --enable-__cxa_atexit --disable-multilib --libdir=/usr/lib --libexecdir=/usr/lib --enable-clocale=gnu --disable-libstdcxx-pch --with-tune=generic Thread model: posix gcc version 4.3.1 20080626 (prerelease) (GCC) You are also running a prerelease of gcc 4.3.1, so this might be a factor here. In the end it does not matter since we cannot just tell people to upgrade their broken compiler, but we should at least attempt to work around some problems like the above. 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.0.6.alpha0 released
Hi, it still breaks on -O3 and -O2 iirc as when I tested... it should be lowered to -O1 to work always, anyway adding only those 2 mentioned earlier flags (-fno-crossjumping -fno-reorder-blocks) makes it work, I though rather about looking for what compiler versions it fails and patching it in those cases like it is done in clisp for example... I also agree -O6 is same as -O3, anyway it's what it is set to in sources... it was also confirmed to occur in not prerelease version of gcc 4.3.1 (see my earlier mail, tested it on friend's debian machine...) - simple solution would be to disable crossjumpung and reorder-blocks for all, but some system might benefit from it... that's why I'm looking into if it happens for all 4.3 or only 4.3.1 cheers, Andrzej. --~--~-~--~~~---~--~~ 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.0.6.alpha0 released
So... I can't replicate this segfault on either OS X or Linux. Could you remind me of precisely what hardware/OS you're using and whether or not you built from source or used a pre-compiled binary. It's 32 bit Arch Linux current, GCC 4.3.1 (patched to snapshot from 2008 06 26), GlibC 2.8, Kernel 2.6.25.11, there's cpuinfo: processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP 2600+ stepping: 0 cpu MHz : 2091.162 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up ts bogomips: 4186.95 clflush size: 32 Also, I think it is better to fix segfaults than to just document them. I totaly agree, unless they cannot be tracked before another release I guess... cheers, Andrzej. --~--~-~--~~~---~--~~ 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.0.6.alpha0 released
Hi again,
was trying to track that segfault in tachyon doctest, it happens
during show(t) in texture example, that's in:
t = Tachyon(camera_center=(2,5,4), look_at=(2,0,0), raydepth=6)
t.light((10,3,4), 1, (1,1,1))
t.texture('mirror', ambient=0.05, diffuse=0.05, specular=.9,
opacity=0.9, color=(.8,.8,.8))
t.texture('grey', color=(.8,.8,.8), texfunc=3)
t.plane((0,0,0),(0,0,1),'grey')
t.sphere((4,-1,1), 1, 'mirror')
t.sphere((0,-1,1), 1, 'mirror')
t.sphere((2,-1,1), 0.5, 'mirror')
t.sphere((2,1,1), 0.5, 'mirror')
show(t)
I noticed that it happens for texfunc 3 and 5 and only if there is at
least one sphere with mirror material (they work when there is no
mirror sphere in scene)... I cannot say how long it is like that, it
was 3.0.4 when I triggered doctest failure in ssmod and was looking
into any wrong output in test.log when I found it... btw - other
texfuncs that don't include images (7,8,9) and those two so (3,5)
works, for example I'm able to get image with texfunc=1...
I don't know if it helps, it can be something in tachyon by itself, if
yes it can be good idea to mention it in documentation of texfunc
and/or change doctest to use for example texfunc=1?
cheers,
Andrzej.
--~--~-~--~~~---~--~~
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.0.6.alpha0 released
On Jul 18, 1:01 am, John Cremona [EMAIL PROTECTED] wrote: Hi John, Following Ansrzej's report I tried the same thing. For me the test always takes 2.0-2.1s but the 5th or 6th time I got the failure: sage -t devel/sage/sage/modular/ssmod/ssmod.py ** SNIP /home/jec/sage-3.0.6.alpha0/tmp/.doctest_ssmod.py [2.1 s] exit code: 1024 -- The following tests failed: sage -t devel/sage/sage/modular/ssmod/ssmod.py Total time for all tests: 2.1 seconds -- after that another 10 tests of that file went ok (and only took 2s). John William and I poked around and it seems to be LinBox related, more specifically computing the charpoly mod p with LinBox 1.1.6.rc0 or later, which was updated from 3.0.3 to 3.0.4. We are tracking the issue at #3671. Clement has been notified and we are hoping to put this to bed today by switching to the generic charpoly implementation which in this case should not be much slower. Once [If?] we nail the bug in LinBox we can then switch back. 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.0.6.alpha0 released
Following Ansrzej's report I tried the same thing. For me the test always takes 2.0-2.1s but the 5th or 6th time I got the failure: sage -t devel/sage/sage/modular/ssmod/ssmod.py ** File /home/jec/sage-3.0.6.alpha0/tmp/ssmod.py, line 14: sage: D[:3] Expected: [ (Vector space of degree 33 and dimension 1 over Finite Field of size 97 Basis matrix: [ 0 0 0 1 96 96 1 96 96 0 2 96 96 0 1 0 1 2 95 0 1 1 0 1 0 95 0 96 95 1 96 0 2], True), (Vector space of degree 33 and dimension 1 over Finite Field of size 97 Basis matrix: [ 0 1 96 75 16 81 22 17 17 0 0 80 80 1 16 40 74 0 0 96 81 23 57 74 0 0 0 24 0 23 73 0 0], True), (Vector space of degree 33 and dimension 1 over Finite Field of size 97 Basis matrix: [ 0 1 96 90 90 7 7 6 91 0 0 91 6 13 7 0 91 0 0 84 90 6 0 6 0 0 0 90 0 91 7 0 0], True) ] Got: [ (Sparse vector space of degree 33 and dimension 2 over Finite Field of size 97 Basis matrix: [ 1 0 18 25 45 86 70 21 62 86 55 84 33 53 48 75 34 83 58 79 55 54 35 4 11 2 48 94 3 6 85 35 61] [ 0 1 93 65 65 45 21 29 9 66 80 50 46 24 10 35 92 15 31 21 46 8 95 72 72 52 68 43 72 12 92 56 90], True), (Sparse vector space of degree 33 and dimension 2 over Finite Field of size 97 Basis matrix: [ 1 0 76 6 6 80 32 36 4 46 31 62 18 82 79 75 79 12 9 0 25 31 12 89 8 50 15 0 42 59 68 82 84] [ 0 1 51 72 45 8 9 16 11 41 55 55 26 17 48 19 26 21 50 92 83 48 60 90 45 69 87 70 90 70 9 82 4], True), (Sparse vector space of degree 33 and dimension 3 over Finite Field of size 97 Basis matrix: [ 1 0 0 79 2 61 77 49 86 71 36 69 24 81 0 78 30 43 78 61 90 63 92 58 69 87 32 87 0 45 41 3 40] [ 0 1 0 6 42 92 6 25 42 72 15 40 56 28 37 14 16 62 51 67 48 69 4 49 83 30 82 91 20 45 84 21 94] [ 0 0 1 61 40 63 18 19 55 62 40 78 91 10 54 0 61 73 87 90 35 4 93 91 79 77 35 42 20 26 2 35 60], True) ] ** File /home/jec/sage-3.0.6.alpha0/tmp/ssmod.py, line 26: sage: len(D) Expected: 9 Got: 6 ** 1 items had failures: 2 of 15 in __main__.example_0 ***Test Failed*** 2 failures. For whitespace errors, see the file /home/jec/sage-3.0.6.alpha0/tmp/.doctest_ssmod.py [2.1 s] exit code: 1024 -- The following tests failed: sage -t devel/sage/sage/modular/ssmod/ssmod.py Total time for all tests: 2.1 seconds -- after that another 10 tests of that file went ok (and only took 2s). John 2008/7/17 Andrzej Giniewicz [EMAIL PROTECTED]: Hi, small report - compiled fine, all tests passed (but that's what was reported by make test)... looking into test.log there's still segfault with tachyon test: sage -t devel/sage/sage/plot/tachyon.pysh: line 1: 2 Naruszenie ochrony pamięci tachyon /root/.sage//temp/ginland/23251//tmp_12.dat -format PNG -o /root/.sage//temp/ginland/23251//test.png /dev/null about ssmod, there's something strange in it. I run it about 20 times (as there were 2 failures / 150 tests it seems I made not enough tests to hit it), passed all the time, but look at speed difference, 19 times it was around 8 seconds, once more than 220 seconds! to make it clear, in both cases I had enough free memory (but long case took 50mb more), and I didn't had other apps running than test and top to make sure... no cron jobs for hour etc... I don't know if there should be such huge difference in same test run in same environment [EMAIL PROTECTED] sage]# sage -t devel/sage/sage/modular/ssmod/ssmod.py sage -t devel/sage/sage/modular/ssmod/ssmod.py [8.8 s] -- All tests passed! Total time for all tests: 8.8 seconds [EMAIL PROTECTED] sage]# sage -t devel/sage/sage/modular/ssmod/ssmod.py sage -t devel/sage/sage/modular/ssmod/ssmod.py [221.5 s] -- All tests passed! Total time for all tests: 221.5 seconds cheers, Andrzej. --~--~-~--~~~---~--~~ 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.0.6.alpha0 released
Installed fine and all tests passed on amd64 hardy heron.
On Wed, Jul 16, 2008 at 11:48 PM, mabshoff [EMAIL PROTECTED] wrote:
Hello folks,
this is 3.0.6.alpha0. This release is a mix of bug fixes and new
features. Nothing crazy has been merged so far and it is unclear at
the moment how things will develop until ISSAC. I have a bunch of
Solaris build fixes sitting on my box that have not been merged due to
lack of time (I am leaving for ECM in about an hour), but expect
steady progress on that front in 3.0.6. As usual please review patches
and spkgs since we have a boatload of them sitting in trac.
Sources and a binary for sage.math are in the usual place:
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.6/sage-3.0.6.alpha0.tar
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.6/sage-3.0.6.alpha0-sage.math-only-x86_64-Linux.tar.gz
As usual please report problems and testing results.
Cheers,
Michael
#3232: Martin Albrecht: wrap NTL's BKZ [Reviewed by Ralph-Philipp
Weinmann]
#3531: Gary Furnish: create optional boehm_gc.spkg [Reviewed by
Michael Abshoff]
#3532: Gary Furnish: create optional gdbm.spkg [Reviewed by Michael
Abshoff]
#3554: Mike Hansen: improve M2 pexpect interface [Reviewed by Gary
Furnish]
#3564: William Stein: optimize sage startup: don't import sympy by
default [Reviewed by Michael Abshoff]
#3579: Emily Kirkman: bug in RandonGNP graph constructor [Reviewed by
Robert Miller]
#3592: Ondrej Certik: update sympy to the 0.6.0 release [Reviewed by
Michael Abshoff]
#3601: Anne Schilling: Reimplementation of tensor products [Reviewed
by Mike Hansen]
#3614: Gary Furnish: pbuild broken by finance [Reviewed by Michael
Abshoff]
#3626: Tom Boothby: Graph.set_boundary only takes lists [Reviewed by
Robert Miller]
#3629: Clement Pernet: givaro-3.2.11 installs its own libgmpxx.{so,a}
[Reviewed by Michael Abshoff]
#3650: Gary Furnish: Infinite recursion in pbuild by recursive pxd
imports [Reviewed by Michael Abshoff]
#3651: John Cremona: elliptic curves -- bug in L_ratio() [Reviewed by
Chris Wuthrich]
#3657: Carlo Hamalainen: Documentation for latin squares, DLXCPP;
minor fixes [Reviewed by Mike Hansen]
#3632: Chris Wuthrich, David Harvey: small bug in p-adic heights
[Reviewed by David Harvey, Chris Wuthrich]
#3647: Michael Abshoff: remove - static-libgcc from lcalc's CFLAGS)
[Reviewed by Mike Hansen]
#3648: Carl Witty, David Harvey: complex(pari(...)) fails [Reviewed by
David Harvey, Carl Witty]
#3660: Anne Schilling, Mike Hansen: add documentation to the reference
manual for crystals and root systems [Reviewed by Mike Hansen]
#3661: Nicolas Thiery, Mike Hansen: move sage/combinat/family.py into
the main tree [Reviewed by Mike Hansen]
#3667: William Stein: notebook -- if user history can't be loaded from
disk make it blank (much better than making entire notebook not work
at all) [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.0.6.alpha0 released
Installed fine and all tests passed, with these flags set:
SAGE_BUILD_THREADS=2
SAGE_PBUILD=yes
on here:
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
John
2008/7/17 David Joyner [EMAIL PROTECTED]:
Installed fine and all tests passed on amd64 hardy heron.
On Wed, Jul 16, 2008 at 11:48 PM, mabshoff [EMAIL PROTECTED] wrote:
Hello folks,
this is 3.0.6.alpha0. This release is a mix of bug fixes and new
features. Nothing crazy has been merged so far and it is unclear at
the moment how things will develop until ISSAC. I have a bunch of
Solaris build fixes sitting on my box that have not been merged due to
lack of time (I am leaving for ECM in about an hour), but expect
steady progress on that front in 3.0.6. As usual please review patches
and spkgs since we have a boatload of them sitting in trac.
Sources and a binary for sage.math are in the usual place:
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.6/sage-3.0.6.alpha0.tar
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.6/sage-3.0.6.alpha0-sage.math-only-x86_64-Linux.tar.gz
As usual please report problems and testing results.
Cheers,
Michael
#3232: Martin Albrecht: wrap NTL's BKZ [Reviewed by Ralph-Philipp
Weinmann]
#3531: Gary Furnish: create optional boehm_gc.spkg [Reviewed by
Michael Abshoff]
#3532: Gary Furnish: create optional gdbm.spkg [Reviewed by Michael
Abshoff]
#3554: Mike Hansen: improve M2 pexpect interface [Reviewed by Gary
Furnish]
#3564: William Stein: optimize sage startup: don't import sympy by
default [Reviewed by Michael Abshoff]
#3579: Emily Kirkman: bug in RandonGNP graph constructor [Reviewed by
Robert Miller]
#3592: Ondrej Certik: update sympy to the 0.6.0 release [Reviewed by
Michael Abshoff]
#3601: Anne Schilling: Reimplementation of tensor products [Reviewed
by Mike Hansen]
#3614: Gary Furnish: pbuild broken by finance [Reviewed by Michael
Abshoff]
#3626: Tom Boothby: Graph.set_boundary only takes lists [Reviewed by
Robert Miller]
#3629: Clement Pernet: givaro-3.2.11 installs its own libgmpxx.{so,a}
[Reviewed by Michael Abshoff]
#3650: Gary Furnish: Infinite recursion in pbuild by recursive pxd
imports [Reviewed by Michael Abshoff]
#3651: John Cremona: elliptic curves -- bug in L_ratio() [Reviewed by
Chris Wuthrich]
#3657: Carlo Hamalainen: Documentation for latin squares, DLXCPP;
minor fixes [Reviewed by Mike Hansen]
#3632: Chris Wuthrich, David Harvey: small bug in p-adic heights
[Reviewed by David Harvey, Chris Wuthrich]
#3647: Michael Abshoff: remove - static-libgcc from lcalc's CFLAGS)
[Reviewed by Mike Hansen]
#3648: Carl Witty, David Harvey: complex(pari(...)) fails [Reviewed by
David Harvey, Carl Witty]
#3660: Anne Schilling, Mike Hansen: add documentation to the reference
manual for crystals and root systems [Reviewed by Mike Hansen]
#3661: Nicolas Thiery, Mike Hansen: move sage/combinat/family.py into
the main tree [Reviewed by Mike Hansen]
#3667: William Stein: notebook -- if user history can't be loaded from
disk make it blank (much better than making entire notebook not work
at all) [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.0.6.alpha0 released
Hi, small report - compiled fine, all tests passed (but that's what was reported by make test)... looking into test.log there's still segfault with tachyon test: sage -t devel/sage/sage/plot/tachyon.pysh: line 1: 2 Naruszenie ochrony pamięci tachyon /root/.sage//temp/ginland/23251//tmp_12.dat -format PNG -o /root/.sage//temp/ginland/23251//test.png /dev/null about ssmod, there's something strange in it. I run it about 20 times (as there were 2 failures / 150 tests it seems I made not enough tests to hit it), passed all the time, but look at speed difference, 19 times it was around 8 seconds, once more than 220 seconds! to make it clear, in both cases I had enough free memory (but long case took 50mb more), and I didn't had other apps running than test and top to make sure... no cron jobs for hour etc... I don't know if there should be such huge difference in same test run in same environment [EMAIL PROTECTED] sage]# sage -t devel/sage/sage/modular/ssmod/ssmod.py sage -t devel/sage/sage/modular/ssmod/ssmod.py [8.8 s] -- All tests passed! Total time for all tests: 8.8 seconds [EMAIL PROTECTED] sage]# sage -t devel/sage/sage/modular/ssmod/ssmod.py sage -t devel/sage/sage/modular/ssmod/ssmod.py [221.5 s] -- All tests passed! Total time for all tests: 221.5 seconds cheers, Andrzej. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
