On 6 Jun., 15:31, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: > I've build Sage 4.4.3 on a Sun Blade 1000 but when running the long doctests, > the output appears to hang. But the actual doctest command is not shown > properly. > > First the output of 'make ptestlong' showed this: > > sage -t -long devel/sage/sage/modular/abvar/lseries.py > [10.2 s] > sage -t -long devel/sage/sage/modular/abvar/homspace.py > [171.9 s] > sage -t -long devel/s > > then on another occasion it stalled at the same place. > > sage -t -long devel/sage/sage/modular/abvar/lseries.py > [10.2 s] > sage -t -long devel/sage/sage/modular/abvar/homspace.py > [171.8 s] > sage -t -long devel/sa
The output buffer isn't flushed. You could try "-verbose" to get closer to the doctest actually hanging. -Leif > I wondered if this could be a lack of memory (the machine only has 2 GB), but > there are no messages about a lack of memory, vmstat shows a low scan rate > (sr) > > drkir...@redstart:~$ vmstat 10 > kthr memory page disk faults cpu > r b w swap free re mf pi po fr de sr s6 sd -- -- in sy cs us sy > id > 0 0 0 9845200 1634144 306 1476 16 78 77 0 1 0 9 0 0 255 2852 214 46 6 > 49 > 0 0 0 9675816 1384296 80 1136 0 3 3 0 0 0 0 0 0 302 7307 174 92 8 > 0 > 0 0 0 9679088 1385816 84 1187 0 0 0 0 0 0 25 0 0 334 8152 204 92 8 > 0 > 0 0 0 9671840 1380712 77 1121 0 1 1 0 0 0 0 0 0 301 7284 176 92 7 > 0 > 0 0 0 9614728 1373816 71 695 0 0 0 0 0 0 0 0 0 287 5485 170 93 6 > 0 > 0 0 0 9675328 1383760 78 1187 0 3 3 0 0 0 7 0 0 301 7694 175 92 8 > 0 > 0 0 0 9637248 1352144 15 365 0 0 0 0 0 0 17 0 0 325 1461 191 98 2 > 0 > 0 0 0 9634304 1348968 0 4 0 0 0 0 0 0 0 0 0 301 207 171 99 1 > 0 > > and 'prstat' does not show excessive memory usage by anything. > > PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP > 20550 drkirkby 209M 137M run 20 0 0:26:09 49% python/1 > 20797 drkirkby 168M 97M cpu0 10 0 0:06:34 50% python/1 > 15601 drkirkby 9528K 7896K sleep 59 0 0:00:08 0.0% python/3 > 20795 drkirkby 8704K 6352K sleep 59 0 0:00:00 0.0% python/1 > 20548 drkirkby 8664K 6312K sleep 59 0 0:00:01 0.0% python/1 > 19006 drkirkby 6728K 5160K sleep 59 0 0:00:00 0.0% python/1 > 20716 root 8416K 4816K sleep 59 0 0:00:00 0.0% sshd/1 > 20377 root 8408K 4352K sleep 59 0 0:00:00 0.0% sshd/1 > 15602 drkirkby 9072K 4120K sleep 59 0 0:00:01 0.0% python/1 > 15603 drkirkby 9072K 4120K sleep 59 0 0:00:01 0.0% python/1 > 20869 drkirkby 4496K 4104K cpu1 39 0 0:00:00 0.1% prstat/1 > 499 root 9192K 3424K sleep 59 0 0:00:02 0.0% snmpd/1 > 88 root 4320K 2984K sleep 59 0 0:00:11 0.0% nscd/26 > 306 root 5344K 2920K sleep 59 0 0:00:03 0.0% fmd/12 > 20723 drkirkby 8192K 2736K sleep 59 0 0:00:00 0.0% sshd/1 > Total: 59 processes, 164 lwps, load averages: 2.01, 2.01, 2.03 > > Has anyone got any ideas? > > Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
