The self-hosted runner fails fast if its base directory is unwritable or the mount hangs.
What's wrong with this entry?
Startup creates and access-checks the base directory under a timeout so an unwritable or hung mount fails immediately rather than partway through a run.
- a timeout exits the process with a hint to check mount health
- other failures throw with instructions to pass
--base-diror setSELF_HOSTED_RUNNER_BASE_DIR
SELF_HOSTED_RUNNER_BASE_DIR
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.224
Runner management tools require a first-party login and say so
Both mention base self hosted runner
-
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