CI job exits 2 with no test results and an empty report — what is code 2?

Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.

Pipeline step fails, the report artefact is empty, and the only thing in the log is the process exiting 2. When tests actually fail we get 1 and a report. What is 2?

config ci cli

asked by Yusuf Demir

2 answers

Accepted answer
Configuration or usage error. Nothing ran, which is why there is no report.
text
```
0    success
1    failure — scenario failures, a gate not met, an unexpected runtime error
2    configuration or usage error
3    lint errors
130  cancelled
```
Everything in this area lands on 2: unknown project, an environment that is not declared or has no file, invalid YAML, a schema issue, an unresolved ${VAR}, a literal secret, a bad flag value.
The message is on stderr rather than in the report. If your CI only captures stdout, that is why the log looks empty — add --json and you get the structured error as one JSON line on stderr with code, message, hint and docsUrl.
answered by Reeta NandalSDODS team
Make it its own step so the failure names itself:
bash
```
sdods config validate
```
Then the pipeline distinguishes "the config is broken" from "the tests are red" without anybody reading exit codes. Same trick for lint, which is code 3 — sdods run lints first, so a tag mistake also stops you before any browser starts.
answered by Priya VenkateshSDODS team

Know the answer?

Wrap commands and output in triple backticks and they will render as a code block.

Checking whether you’re signed in…

Have a different question? Ask it.

CI job exits 2 with no test results and an empty report — what is code 2?

2 answers

Know the answer?

Related