You'll notice
Useful2 Signal2
Self-hosted runner failures now report the killing signal, distinguishing crashes from ordinary exits.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a self-hosted runner's child process fails, the reported result now includes the signal that terminated it as well as the exit code, which distinguishes a crash or an out-of-memory kill from an ordinary non-zero exit.
Details
- The signal appears in the posted failure payload and in both log lines, the initial attempt and the retry.
- Self-hosted runners only.
Evidence
exitSignal
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