GitHub Actions "Error: Process completed with exit code 1"

By Kaveh Alemi·Latchkey

A command in a run step exited non-zero, so the shell failed the step; exit code 1 is the generic "the command itself reported failure" status, not an infrastructure problem.

What this error means

A run step ends with "Error: Process completed with exit code 1." The real error is in the command output just above this line.

npm ERR! Test failed.  See above for more details.
Error: Process completed with exit code 1.

Common causes

The command genuinely failed

Tests failed, a lint gate tripped, or a build error occurred, and the tool returned exit code 1.

pipefail surfacing an upstream failure

A piped command failed and set -o pipefail (the default in Actions bash) propagated the non-zero status.

How to fix it

Read the output above the exit line

1. Scroll up to the actual error the tool printed.
2. Reproduce the failing command locally with the same inputs.
3. For pipelines, isolate which command in the pipe failed.
4. Fix the underlying failure rather than masking the exit code.

Avoid hiding real failures

Do not append || true to silence a failing command unless the failure is truly non-fatal; that hides regressions.

How to prevent it

• Treat exit code 1 as a real signal, not noise.
• Keep step output readable so the cause is easy to find.
• Reserve || true for genuinely optional commands.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions