Hi David, I was "manually" testing #4000's Solaris GCC workaround against a trial 4.6.alpha3 compiled earlier by Buildbot. I can reduce the number of test jobs. Just let me know.
Sincerely, Mitesh On 10/08/2010 04:12 AM, Dr. David Kirkby wrote: > I've noticed my machine (which is a buildbot slave) was under high load > (fan noise raises a little), and when I checked using 'prstat', I could > see buildbot was using the system. > > PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP > 19840 buildbot 301M 232M run 50 0 0:02:04 9.2% python/1 > 16312 buildbot 207M 139M run 41 0 0:04:56 8.5% python/1 > 19018 buildbot 170M 101M cpu4 50 0 0:02:40 8.4% python/1 > 22254 buildbot 177M 110M run 40 0 0:00:39 7.7% python/1 > 22307 buildbot 183M 116M cpu5 51 0 0:00:37 7.5% python/1 > 22239 buildbot 182M 116M cpu3 50 0 0:00:38 7.5% python/1 > 22344 buildbot 188M 121M run 40 0 0:00:33 7.0% python/1 > 22408 buildbot 179M 114M cpu0 40 0 0:00:26 6.5% python/1 > 22590 buildbot 169M 98M cpu7 50 0 0:00:10 4.3% python/1 > 22576 buildbot 179M 111M cpu6 50 0 0:00:11 4.2% python/1 > 22593 buildbot 179M 113M cpu1 40 0 0:00:06 2.6% python/1 > 16380 drkirkby 1385M 1332M run 49 0 3:59:22 2.4% VirtualBox/21 > 22603 buildbot 32M 26M sleep 59 0 0:00:02 0.9% maxima/1 > 22468 buildbot 26M 6288K sleep 59 0 0:00:05 0.8% gp/1 > 22633 buildbot 109M 49M run 40 0 0:00:01 0.6% python/1 > Total: 208 processes, 552 lwps, load averages: 13.64, 13.36, 9.45 > > But the buildbot page at > > http://build.sagemath.org/sage/waterfall > > shows my machine as idle. I thought it might take some time to update, > but it's been busy for some time now (10-15 minutes), and still the > display is not updated to indicate a build is in progress. > > 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
