Skip to main content
aspect ci runner-health-check runs the runner health check by itself, without a build. Every Bazel task already runs this check during its setup phase; this command is for a pipeline step or a debugging session that wants only the check.
On an Aspect Workflows runner it:
  1. Waits for cache warming to finish.
  2. Prints the last runner health check and the warming status.
  3. Probes the runner’s Bazel server, and marks the runner unhealthy if the server is stuck.
It exits non-zero when the Bazel server is unhealthy. Off a Workflows runner there’s no runner to check, so it prints a line saying so and exits 0.

​
Options

The check starts Bazel on the runner’s own output base, so it takes the same Bazel flag options as the build tasks and no --output-base of its own.