[Buildbot-devel] buildslaves & sleep

[Charles Lepple]

Yes, if the system goes to sleep for long enough, the master will consider the slave to be dead.

I think the "wake on network access" feature is for incoming connections, and from the perspective of the buildslave, that connection is outgoing.

I don't mind having a delay while the buildslave retries its connection, but the problem I have is that the system does its "dark wake", reconnects, and then goes back to sleep. If a build comes in, then eventually it fails with an exception.

Wrapping commands in "caffeinate" should work (it works in SSH contexts) but something is not grabbing the sleep assertion. (In my case, the buildslave is started from a launchd plist. Tested on 10.9 and 10.10.)

Trying a latent buildslave might be the next idea on my list.

On Jun 24, 2015, at 5:51 PM, Vitali Lovich <vlovich at gmail.com> wrote:

> Oh.  Maybe not.  What about the TCP keep alive?  Wouldn’t the master think that the slave is dead?
> 
> -Vitali
> 
>> On Jun 24, 2015, at 2:50 PM, Dan Kegel <dank at kegel.com> wrote:
>> 
>> If it wakes well on network access, does it even need to be latent?
>> 
>> On Wed, Jun 24, 2015 at 2:49 PM, Vitali Lovich <vlovich at gmail.com> wrote:
>>> Hi,
>>> 
>>> In the interest of conserving power I would love to let my buildslaves go to sleep when idle.  All my buildslaves are OS X & will wake on network access.
>>> Would implementing all of this as a latent buildslave be the best next-step?