CircleCI was unable to execute the job to completion, because the CircleCI runner received a kill signal midway through the job.
When running your jobs in CircleCI, you may encounter this error causing your builds to not complete, almost randomly.
This error can also be in combination with
CircleCI received exit
code 1 or
CircleCI received exit code 137.
These exit codes and errors typically go in combination with resource constraints. Please take a look at the resource tab on your job's page.
If your graph looks similar to this, please consider upgrading your resource class to a larger one.
If you are continuing to see resource class exhaustion during your build, and you are testing your application, you may take a look at
test splitting which involves splitting your tests up to separate containers which can reduce resource usage and even speed up your tests.
Article is closed for comments.