I've been plagued by a buildmaster that gets stuck and doesn't serve jobs fairly frequently. My theory was that it was caused by doing 'sudo initctl reload buildmaster' (which is said to be dangerous)... but today it happened again without that. This time when I looked at the master's log, I noticed something: the line
2017-07-24 10:33:32-0700 [-] acquireLocks(slave <BuildSlave 'g-speak-rbb-osx1010-2'>, locks []) appeared with no following releaseLocks. Hey, that's the slave where I did 'kill -TSTP' to pause the buildslave. Light bulb goes on. This is with 0.8.mumble. Is it still possible with 0.9.x? _______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
