On 12/7/10 4:41 AM, Robert Bradshaw wrote:
That's an interesting idea, but it's not easy to expose that information. The way it works is that a build slave requests a list of tickets, rates them according to its own internal settings (which may be different for each bot), and then starts on a ticket (notifying the server to avoid overlap). I suppose as well as a pending field list, one could add something that collects different bots ratings at different points in time and their respective speeds and does an estimate.
Or you could maybe pass the work on to the slave: after sorting tickets, the slave replies with a time estimate for each ticket. The server then updates the page. The bot could then send updated estimates whenever too. In the setup for a slave, it could ask for the amount of time it takes to run testall (or compute that from a test run, or take a running average over several tickets) and use that as a multiplier.
Or maybe it's just better to report the lowest rating a ticket receives from a slave, and let the user use that as a gauge for how soon the ticket would be tested.
Thanks, Jason -- 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
