Skip to content

Commit 76b9478

Browse files
committed
docs: exit code 112 for cloud api network errors
1 parent b173f5d commit 76b9478

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

docs/app/references/command-line.mdx

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -634,7 +634,7 @@ the exit code will be 1.
634634
635635
```text
636636
## Spec with two failing tests
637-
$ cypress run
637+
$ cypress run --posix-exit-codes
638638
...
639639
Tests Passing Failing
640640
✖ 1 of 1 failed (100%) 00:22 17 14 2
@@ -644,6 +644,23 @@ $ echo $?
644644
1
645645
```
646646
647+
When you use the `--posix-exit-codes` flag in a run that requires [Cypress Cloud](/cloud/get-started/introduction), and the Cypress application cannot communicate with the Cypress Cloud API due to a network error, the exit code will be `112`. Runs that use either `--record` or `--parallel` require communication with Cypress Cloud API.
648+
649+
```text
650+
$ cypress run --posix-exit-codes --parallel --group=foo --ciBuildId=ciBuildId123
651+
We encountered an unexpected error communicating with our servers.
652+
653+
RequestError: Error: ESOCKETTIMEDOUT
654+
655+
Because you passed the --parallel flag, this run cannot proceed since it requires a valid response from our servers.
656+
657+
The --group flag you passed was: foo
658+
The --ciBuildId flag you passed was: ciBuildId123
659+
660+
$ echo $?
661+
112
662+
```
663+
647664
If Cypress could not run for some reason (for example if no spec files were
648665
found) then the exit code will be 1.
649666

0 commit comments

Comments
 (0)