The addition of the buildbot to Sage should be a good thing. But it seems to get very little use. I know the Wireshark projects runs their buildbots 24/7. Any failures are emailed to the developers, along with a list of who has committed source since the last successful build. I appreciate that its not practical to do this on all machines (I for one would not appreciate if 'hawk' was constantly running Sage tests.. But its 10 days since the buildbot was last run, yet in that time, there has clearly been tickets committed.
Perhaps a list should be drawn up on how often its acceptable to run tests on hosts, and perhaps make better use of the resources. For the two machines I'm responsible for, I would say: t2 - no limits hawk - up to 3 builds per day. 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
