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.
Merged a branch this morning and the test job now ends in seconds:
Error: Process completed with exit code 3.There is no HTML report and no failing scenario to look at, so my first instinct was that the runner is broken. 3 is not in the list of codes I had memorised (0, 1, 2).
Accepted answer
3 is lint errors. sdods run lints the project before it generates or runs anything, and stops if lint found errors — which is why there is no report: nothing ran.
The findings are printed on stderr just above that line; if your CI collapses stderr, run it directly:
sdods lint -p demo-shopSomebody's merge almost certainly added a scenario with two suite tags or no layer tag. Fix that. --no-lint exists and will make your job go green, and it is the wrong lever — you would be shipping a scenario that no tag expression selects correctly.
The two errors that account for nearly all of these, in my experience of policing this: a scenario with both @smoke and @regression, and a scenario with no layer tag at all after somebody copied it into a new file.
sdods lint -p demo-shop --fix-tags--fix-tags adds a missing layer tag when the folder makes it obvious. It will not choose a suite tag for you, and it should not — that is a decision about how often the scenario runs.
Small pipeline change that removes the confusion permanently: run lint as its own step before the suite step. Then the failing step is called "lint" and nobody spends fifteen minutes wondering why the test job produced no tests.
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.