All tests passed on my intel mac pro, running OS X 10.4.11. -M. Hampton
On May 3, 8:07 am, "John Cremona" <[EMAIL PROTECTED]> wrote: > Two successful builds of rc0 (32 and 64 bit linux). The 64-bit one > seems to have stalled doing testall at this point: > > sage -t devel/sage/sage/dsage/dist_functions/all.py > [1.3 s] > sage -t devel/sage/sage/dsage/scripts/nodoctest.py (skipping) -- > nodoctest.py file in directory > sage -t devel/sage/sage/dsage/scripts/dsage_worker.py (skipping) -- > nodoctest.py file in directory > sage -t devel/sage/sage/dsage/scripts/__init__.py (skipping) -- > nodoctest.py file in directory > sage -t devel/sage/sage/dsage/scripts/dsage_setup.py (skipping) -- > nodoctest.py file in directory > sage -t devel/sage/sage/dsage/web/web_server.py > [1.3 s] > sage -t devel/sage/sage/dsage/tests/testdoc.py > > which has not moved for at least haf an hour. > > Switching do a different window on the same machine, "ps -ax" shows this: > > [EMAIL PROTECTED] ux > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jec 10107 0.0 0.0 150936 3832 ? S Apr10 0:00 > python /home/jec/sage-3.0.alpha3/local/bin/twistd -d > /home/jec/.sage/dsage --pidfile=server.pid --log > jec 17257 0.0 0.0 144636 3976 ? S Apr15 0:00 > python /home/jec/sage-3.0.alpha5/local/bin/twistd -d > /home/jec/.sage/dsage --pidfile=server.pid --log > jec 9518 0.0 0.0 144648 3848 ? S Apr19 0:00 > python /home/jec/sage-3.0.alpha6/local/bin/twistd -d > /home/jec/.sage/dsage --pidfile=server.pid --log > jec 2656 0.0 0.0 144672 3956 ? S Apr20 0:00 > python /home/jec/sage-3.0.rc0/local/bin/twistd -d > /home/jec/.sage/dsage --pidfile=server.pid --logfil > jec 31253 0.0 0.0 151016 3864 ? S Apr21 0:00 > python /home/jec/sage-3.0.rc1/local/bin/twistd -d > /home/jec/.sage/dsage --pidfile=server.pid --logfil > jec 20989 0.0 0.0 144724 3916 ? S Apr21 0:00 > python /home/jec/sage-3.0.rc1/local/bin/twistd -d > /home/jec/.sage/dsage --pidfile=server.pid --logfil > jec 24920 0.0 0.0 151008 3860 ? S Apr22 0:00 > python /home/jec/sage-3.0/local/bin/twistd -d /home/jec/.sage/dsage > --pidfile=server.pid --logfile=/h > jec 12580 0.0 0.1 144708 24364 ? S May01 0:00 > python /home/jec/sage-3.0/local/bin/twistd -d /home/jec/.sage/dsage > --pidfile=server.pid --logfile=/h > jec 17881 0.0 0.0 87884 2172 ? S 10:09 0:04 sshd: [EMAIL > PROTECTED]/1 > jec 17882 0.0 0.0 17696 2644 pts/1 Ss 10:09 0:00 -bash > jec 25047 0.0 0.0 15808 1680 pts/1 S+ 12:39 0:00 bash > ./sage --testall > jec 25054 0.0 0.0 15944 1776 pts/1 S+ 12:39 0:00 bash > /home/jec/sage-3.0.1.rc0/local/bin/sage-sage --testall > jec 25066 0.0 0.0 15816 1696 pts/1 S+ 12:39 0:00 bash > /home/jec/sage-3.0.1.rc0/local/bin/sage-maketest > jec 25406 0.0 0.0 15816 1696 pts/1 S+ 12:39 0:00 bash > /home/jec/sage-3.0.1.rc0/sage -t > /home/jec/sage-3.0.1.rc0/devel/sage/sage > jec 25407 0.0 0.0 4004 652 pts/1 S+ 12:39 0:00 tee > -a /home/jec/sage-3.0.1.rc0/tmp/test.log > jec 25414 0.0 0.0 15944 1788 pts/1 S+ 12:39 0:00 bash > /home/jec/sage-3.0.1.rc0/local/bin/sage-sage -t > /home/jec/sage-3.0.1.rc0/devel/sage/sage > jec 25426 0.0 0.0 17708 3708 pts/1 S+ 12:39 0:00 > python /home/jec/sage-3.0.1.rc0/local/bin/sage-test > /home/jec/sage-3.0.1.rc0/devel/sage/sage > jec 10364 0.0 0.0 85816 2056 ? S 12:54 0:00 sshd: [EMAIL > PROTECTED]/4 > jec 10365 0.0 0.0 17692 2608 pts/4 Ss 12:54 0:00 -bash > jec 19763 0.0 0.0 32952 4400 pts/1 S+ 13:02 0:00 > python /home/jec/sage-3.0.1.rc0/local/bin/sage-doctest > /home/jec/sage-3.0.1.rc0/devel/sage/sage/dsage > jec 19764 0.0 0.0 15812 1636 pts/1 S+ 13:02 0:00 sh -c > /home/jec/sage-3.0.1.rc0/local/bin/python > /home/jec/sage-3.0.1.rc0/tmp/.doctest_testdoc.py 1>/t > jec 19765 0.0 0.5 664996 89580 pts/1 S+ 13:02 0:01 > /home/jec/sage-3.0.1.rc0/local/bin/python > /home/jec/sage-3.0.1.rc0/tmp/.doctest_testdoc.py > jec 19805 0.0 0.0 0 0 pts/1 Z+ 13:02 0:00 > [python] <defunct> > jec 19932 0.0 0.0 4600 868 pts/4 R+ 14:00 0:00 ps ux > > which reveals that as well as the stalled run I knew about, there are > 8 other sage processes stuck in limbo. Before I kkill these jobs > (which I certainly will -- it is not even my own machine) -- is there > anything I can do to help diagnose the problem? > > John > > 2008/5/3 elflapper <[EMAIL PROTECTED]>: > > > > > This builds without error on Archlinux (3.0 didn't build with just > > 'make')!!! > > > On May 2, 11:43 pm, mabshoff <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > This is the end of the 3.0.1 release cycle. The build was announced > > > in IRC about eight hours ago, but since I took a long nap in the > > > meantime I never posted to sage-devel ;) > > > > Gary's pbuild has been improved and three bugs have been fixed. > > > Please try it out again for feedback. To use pbuild > > > > export SAGE_PBUILD=yes > > > > before building Sage. The number of threads used during the build of > > > the Sage library is set via SAGE_BUILD_THREADS, i.e. > > > > export SAGE_BUILD_THREADS=8 > > > > for eight threads. Switching between pbuild and normal build is not > > > possible in all cases, so in case of problems nuke the build directory > > > on devel/sage. > > > > Things should "just work" in this release [famous last words], but > > > there are some reported oddities with pexpect behaving badly. We have > > > so far been unable to reproduce and of those issue on a local system > > > [Gary claims testdoc.py hangs for him on sage.math - but it doesn't > > > for me], so if you see anything please let us know. > > > > Sources and binaries are in the usual place: > > > >http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.1/sa... > > > >http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.1/sa... > > > > This is the end of the release cycle. A handful more patches are > > > planned for 3.0.1.final. Anything non-blocker will be considered for > > > 3.0.2. > > > > Cheers, > > > > Michael > > > > Merged in rc0: > > > > #2755: Andrey Novoseltsev: lattice_polytope.py update > > > #3060: Marshall Hampton, Michael Abshoff: update optional biopython > > > package to 1.45 release > > > #3062: Timothy Clemans: implement __oct__ special method for the > > > integers > > > #3070: Robert Miller: bug in SymmetricGroup(1).cayley_graph() > > > #3071: Gary Furnish: Using pbuild does not create site-packages sage > > > symlink > > > #3072: Willem Jan Palenstijn: sage -i numeric-24.2 (and all other > > > experimental packages) fails > > > #3074: Robert Bradshaw: update Cyton to the 0.9.6.14 release > > > #3076: Michael Abshoff: spkg-debian in extcode spkg not executable > > > #3077: Gary Furnish: pbuild does not return properly on failure > > > #3078: Willem Jan Palenstijn: sage's spkg-install doesn't return > > > failure if build failed > > > #3082: William Stein: sage-3.0.1.alpha1: a twist.py doctest failure --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
