You can set a startup timeout for self-hosted runners, otherwise the built-in default applies.
What's wrong with this entry?
The env-var-or-default logic for the self-hosted runner startup timeout moved into its own function.
- Gated on
SELF_HOSTED_RUNNER_STARTUP_TIMEOUT_MS. - Unset or empty still falls back to the built-in default.
SELF_HOSTED_RUNNER_STARTUP_TIMEOUT_MS
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