actions / actions/actions-runner-controller
Actions time out after some amount of time
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
When utilizing the actions runner controller in our clusters within GKE (1.18.20), we've noticed that long running jobs (usually ones over half an hour) will eventually kill themselves while in the process of completing and responds with no exit code. The job seemingly stops reporting to GitHub entirely. Is this known behavior and is there anything we can do to alleviate this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the long-running job behavior with the actions runner controller in the reported GKE 1.18.20 environment, then inspect the runner logs and GitHub reporting status when the job stops. Done means identifying the timeout or failure cause and documenting a verified mitigation for jobs running longer than half an hour.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, github-actions, go, kubernetes
- Domain
- ci-cd, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100