Runner Release 3.1.12

Machine Runner:

• You can now set runner.ssh.advertise_addr_url instead of a fixed runner.ssh.advertise_addr. The runner fetches the SSH rerun address from that URL when a task starts. Use this when something outside the runner assigns the address. The URL must return a host:port.

Container Runner:

• Fixed a leak that occurred when a task was stopped for exceeding its maximum run time. The runner kept watching the task’s pod after that pod had been deleted, leaving a watcher behind for the life of the agent process. An agent that reached the limit repeatedly could accumulate them.

Both Machine and Container Runner:

• Fixed enforcement of the maximum run time (max_run_time, default 5 hours). Two parts of the runner waited on the same internal timeout signal and only one of them could receive it, so the deadline was sometimes missed. A task that overran was then left to run to completion, and its job could still be reported as successful. The same race could also report a task that had genuinely failed as a success. Tasks that reach the limit are now marked failed and stopped as intended.