Self-hosted runners wait for a session's pending work before releasing it.
What's wrong with this entry?
Releasing a session on a self-hosted runner now waits for that session's pending task instead of firing immediately, and cancels the idle timer at the same time. Sessions marked awaiting-action are unaffected.
- Outcomes are now reported separately as
released_true_mid_work,released_falseandrpc_failedrather than one result. - New log lines explain that a session which reports
released=falserespawns on the next poll, or is requeued if the runner is draining or retiring.
self_hosted_release_session
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.238
Self-hosted runner shutdown defers new sessions instead of refusing them outright
Both mention self hosted runner
-
v2.1.238
Self-hosted runner: prefetched-checkout fast path is compiled in but inert
Both mention self hosted runner