Exit Code 1 in CI: What It Means and How to Fix It
Exit code 1 is the generic "something failed" - nearly every tool uses it.
Exit 1 is the most common failure code and carries no specific meaning; the real cause is in the logs.
What it means
A catch-all error. The tool failed but did not use a more specific code.
Common causes
- A test failed, a lint error, a build error.
- A script
exit 1on a checked condition. - A command not found inside a subshell.
How to fix it
Read the lines above the exit; the actual error (a failed assertion, a compiler error) is there. Reproduce the failing command directly.
Related guides
npm ELIFECYCLE / Exit Status Errors - Diagnose Failing npm ScriptsUnderstand npm ELIFECYCLE and non-zero "Exit status" errors in CI - they mean your script failed. How to find…
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…
CI Exit Code Lookup: What Does This Exit Code Mean?Instant lookup for CI/CD process exit codes - enter a code (137, 127, 143…) to see what it means, whether it…