diff --git a/roles/github_runner_cluster/README.md b/roles/github_runner_cluster/README.md index b2e351c8..4aacf65a 100644 --- a/roles/github_runner_cluster/README.md +++ b/roles/github_runner_cluster/README.md @@ -181,6 +181,16 @@ A Mac still has to log in for the agent to run: a launch agent starts with the u A host that got the agent from release 2.19.0 moves over on its next run: the role unloads the node profile's agent from the user's login session when there is one, deletes its property list (also when nobody has logged in, so it cannot load at the next login and start the profile a second time) and loads the daemon. Unloading either kind does not stop the VM, which the job started detached, and loading one runs `colima start`, which does nothing to a running profile. A rerun with nothing changed makes no `launchctl` call that changes anything. With `github_runner_cluster_runtime_autostart` off the role installs, loads and removes none of this. +**Watchdog.** `tasks/runtime_wedged.yml` stops and starts a wedged VM only while the playbook runs, so a VM that wedges between runs stays down, with its node and runner pods, until someone converges the host. With `github_runner_cluster_runtime_watchdog` on (the default, under `github_runner_cluster_runtime_autostart`) the role installs a launchd job beside the start job, `com.exadev.github-runner.colima-watchdog.`, that runs `files/colima-watchdog.sh` every `github_runner_cluster_runtime_watchdog_interval` seconds (a daemon for the profile started at boot, an agent for any other, as for the start job). The script, `run_bounded.pl` and the script's state live under `~/.local/share/exadev-github-runner/colima-watchdog-`, and its log is `~/Library/Logs/