A shutting-down self-hosted runner now finishes assigned sessions instead of refusing them outright.
What's wrong with this entry?
After a SIGTERM, the runner no longer immediately turns away work. A session assigned during shutdown is still served until a defer ceiling or its idle timer releases it, and a session that declines release because a user event is pending gets re-spawned. Only past the ceiling does the runner refuse to start it and put it back on the queue.
- Applies to every self-hosted runner on this build; there is no flag.
- The warning printed on a second signal now reads "Another SIGTERM" rather than "A second SIGTERM".
[runner:shutdown] defer ceiling reached (
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Self-hosted runners report when warm-up finished
Both mention self hosted runner
-
v2.1.236
Self-hosted runner releases a session only after its work finishes
Both mention self hosted runner
-
v2.1.236
Runner waits for sessions to be released before shutting down
Both mention self hosted runner