Ideas concerning buildbot

[Simon Heimberg]

Could somebody check if there are many hg processes hanging around on the 
windows slave? My guess is that hg serve processes from previous test runs 
are blocking the ports, preventing the test in the next run to succeed 
(details in an earlier mail [1]). But I can not test this theory because I 
can not look into the build slave.

Could the notification email be triggered when the number of failed tests 
changes? A mail is (or was?) sent when there is any failure for the first 
time or when it passes again. But on Windows, we have too many failures to 
be triggered on a new one.
(Is the notification email configured? Probably not, the last mail was in 
September.)

Could we "open source" the buildbot configuration? Then we can discuss 
about it and automatically have a backup.


[1] 
http://www.selenic.com/pipermail/mercurial-devel/2014-January/055679.html