build-contract container ends up as Completed in kubernetes on docker-compose timeouts #34
Description
I had a build job that failed due to:
...
An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
But build-contract exits with 0 and thus any pod in kubernetes that runs it will show up as Completed instead of Error. These timeout errors are often transient, so re-running the build-contract once would result in a proper build