Over the last couple weeks, I noticed some failures in our pathogen GH Action workflows that were abnormally long. These were stuck on the setup runtime step of the pathogen-repo-build workflow for hours pulling the docker image before ultimately failing.
Examples:
I'm not sure what's causing the delay in pulling the docker image (network issues?), but we should probably guard against these long running jobs with timeout-minutes.
I don't see a built-in way to set timeout-minutes for composite actions so we could
- add the
timeout command to setup-nextstrain-cli
- add
timeout-minutes to workflows that use setup-nextstrain-cli
Over the last couple weeks, I noticed some failures in our pathogen GH Action workflows that were abnormally long. These were stuck on the setup runtime step of the pathogen-repo-build workflow for hours pulling the docker image before ultimately failing.
Examples:
I'm not sure what's causing the delay in pulling the docker image (network issues?), but we should probably guard against these long running jobs with
timeout-minutes.I don't see a built-in way to set
timeout-minutesfor composite actions so we couldtimeoutcommand tosetup-nextstrain-clitimeout-minutesto workflows that usesetup-nextstrain-cli