General
Process completed with exit code 1
Exit code 1 is the most common CI failure. It means a process returned a generic error. The actual issue is in the output lines ABOVE this message.
Root Cause
A command in your workflow returned a non-zero exit code. This is a catch-all error — the real cause is in the preceding log lines. Common causes: lint errors, test failures, build compilation errors, missing dependencies, or type errors.
How to Fix
- 1Look at the STEP NAME that failed in the workflow run — this tells you which command errored
- 2Read the log lines ABOVE 'Process completed with exit code 1' — the actual error message is there
- 3Common causes: ESLint violations (run 'npx eslint . --fix'), test failures (run 'npm test' locally), TypeScript errors (run 'npx tsc --noEmit'), build failures (run 'npm run build')
- 4Run the exact same command locally to reproduce and fix the error
- 5Push the fix and re-run the workflow
Commands
# Reproduce locally — run the exact step that failed: npm test # if test step failed npm run build # if build step failed npm run lint # if lint step failed npx tsc --noEmit # if typecheck step failed
Prevention
Add 'set -e' to shell scripts, use specific exit code handling, and add pre-commit hooks (lint, typecheck) to catch errors before they reach CI. WarpFix auto-detects these failures and opens fix PRs.
Automate This
WarpFix detects "Process completed with exit code 1" automatically and opens a fix PR — before you even see the error.
WarpFix monitors your GitHub repos 24/7. When CI fails, it identifies the error, generates a fix, validates it in a sandbox, and opens a PR — automatically.
Install WarpFix — Free