is buildbot slave timeout too short?

could you take a look at your logs and estimate how much time it did take to startup? Since twistd doesn't record seconds in the logfiles, you'll have to do this with 'tail -f' and a stopwatch (or some clever programming): measure the elapsed time between the "Loading buildbot.tac" line and the "configuration update complete" lines.

If it's less than 10 or 15 seconds, I'll just bump up the timeout. If it's more than that, I'd be inclined to add a --timeout option to the 'buildbot start' command (and restart and reconfig), since I want to provide earlier feedback about broken startups in the most common case.

And if it is slow for your buildmaster, any idea what's taking so long? It shouldn't be reading any status from disk or interacting with buildslaves at all during startup, so the time it takes should be linear with the complexity of your configuration and with the speed of your machine. Is there something weird going on that's making it slower than usual?

1) Changing timeout to 10seconds for this 0.7.6 release. Lets see if that makes things better.

2) Found a bug in how the error message is generated. It parses the newly-generated logfiles for "Creating BuildSlave". If found, assumes running a slave and if not found, assumes running on a master. However, we can see situations where no logs are yet present on a slave, and this logic incorrectly determines this to be a master. This is not fixed in 0.7.6.

ok, I've bumped the timeout to 10 seconds, in [458]. I'll push the rest of this issue to the next release.

no progress on this yet, bumping to 0.7.8