CI Exit Code Lookup: What Does This Exit Code Mean?

CI Exit Code Lookup: What Does This Exit Code Mean?

Type an exit code to see what killed your job - and whether it is the kind of failure that self-heals.

A non-zero exit code is your job telling you how it died. Enter the code below for a plain-English meaning and the likely fix.

Process exit code

Quick reference

Codes above 128 mean the process was terminated by a signal - subtract 128 to get the signal number (137 = 128 + 9 = SIGKILL).

Related guides

Exit Code 137 Explained: SIGKILL and the OOM Killer in CIWhat exit code 137 means in CI: the process received SIGKILL, almost always from the out-of-memory killer. Ho… Exit Codes and Signals in CI/CD: A Practical GuideA practical guide to process exit codes and signals in CI/CD - what 1, 2, 124, 126, 127, 130, 137, and 143 me… Self-Healing CI: Recovering from OOM-Killed Jobs (Exit 137)Out-of-memory kills (exit 137) are mechanical, not code bugs. See the manual fix and how self-healing CI auto… GitHub Actions Runner Size RecommenderGet a recommended GitHub Actions runner size for your workload - pick the job type and parallelism to avoid p…