Runner goes offline even though (virtual) machine is running and awake. Reboot solves problem.

If you feel that your issue can be categorised as an existing bug or a feature proposal, please use one of the issue templates provided and include as much information as possible.

I am running a triple OS continuous integration script, using the shell executor. The host is macOS, and the VMs are Windows 10 Home and Ubuntu 14.04 Desktop. It works without fail (I really love GitLab's CI!), except when the VMs go a bit of time without being used. Then they go to sleep and the CI service reports as blocked. If I log into the VMs, then usually it works again.

However, frequently that's not enough and I resort to rebooting. This always clears up the problem. Whereas kicking the job via the GitLab interface doesn't resolve the problem, and when I look at the available runners they still show up as missing.

It'd be cool to be able to configure the VM not to go fully to sleep, but the bigger issue is needing to reboot/stop-start* once the VM is woken.

*I haven't tried just stop-starting the runner because a reboot is quick and easy, whereas digging up admin rights is a PITA.