Benji York wrote: > I was thinking of "active" branches that there are buildbot slaves > dedicated to (2.4 at the moment) and the trunk, but (as I mentioned) > non-idleness pretty much kills that idea. I wonder if the slaves that > are known to be dedicated to running buildbot and nothing else could be > flagged as such.
The problem is that even these could do different things simultaneously: I still haven't figured out how to mutually lock out builders that are on the same slave. This is a frequent thing to happen, as people often check-in trunk and backported branch patches nearly simultaneously (which is fine, of course - the machines just have to cater with that). Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
