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?
asked by Yusuf Demir201 ·
CI job exits 2 with no test results and an empty report — what is code 2?
Asked 8,020 views2 answers
2 answers
Accepted answer
Configuration or usage error. Nothing ran, which is why there is no report.
text0 success 1 failure — scenario failures, a gate not met, an unexpected runtime error 2 configuration or usage error 3 lint errors 130 cancelledEverything 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
--jsonand you get the structured error as one JSON line on stderr withcode,message,hintanddocsUrl.answered by Reeta Nandalmaintainer41,280 ·Make it its own step so the failure names itself:
bashsdods config validateThen 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 runlints first, so a tag mistake also stops you before any browser starts.answered by Priya Venkateshmaintainer29,604 ·
Have the same question?
Ask it with the command you ran and the output you got, and it will be answered here.
Ask a questionRelated
- Installing onto a machine with no outbound internet at all0 answers
- Linting only the staged feature files in a pre-commit hook — is --json stable enough?0 answers
- Does colorScheme from the env use: block reach a recording, or only the runner?0 answers
- har record printed no scrub line and the Cookie header is still sitting in the file0 answers
- Locator fragility table is empty in insights but heal report has plenty of rows0 answers