{"version":"2.1.246","anchor":"runner-failures-report-the-signal-that-killed-the-process","canonical_anchor":"runner-failures-report-the-signal-that-killed-the-process","heading":"Runner failures report the signal that killed the process","tier":"notice","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/runner-failures-report-the-signal-that-killed-the-process","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Runner failures report the signal that killed the process\n\nSelf-hosted runner failures now report the killing signal, distinguishing crashes from ordinary exits.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The signal appears in the posted failure payload and in both log lines, the initial attempt and the retry.\n- Self-hosted runners only.\n\n**Evidence**\n\n`exitSignal`\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}