We started getting in multiple projects that use the image cimg/mysql:8.0:
exited with error (exited with 137)
at the end of the “container step” output. The rest of the output seems to be the same as before.
While the step itself fails, it doesn’t fail the job.
Still, this is a strange behavior that seems to have started regardless of code changes, and we are worried it might have unforeseen effects.
Some examples:
https://app.circleci.com/pipelines/github/melio/compliance-aml-monitoring/347/workflows/f83f8cf4-de6f-46da-9728-eeb19cb4dcac/jobs/1224
https://app.circleci.com/pipelines/github/melio/compliance-org-key-individual-service/831/workflows/ad840236-b0aa-4cc4-8f5e-b8ecbb20fae9/jobs/3870
Official reply from support:
A few days ago we introduced a bug whereby sidecar containers were not gracefully shut down, and those containers resulted in a 137 exit status. While the sidecar container step fails, it did not fail the job. As such, while it can look confusing in the UI, it would not impact the result of the job itself.
We addressed this issue last Tuesday shortly after your first job link. As such you should not see this issue from Wednesday 20th onwards.
And indeed the behavior stopped.
