openedx / openedx/openedx-platform
Cache Docker Images cleanup in unit-tests taking more than 9 minutes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
The "Cache Docker Images" step in the unit-tests workflow has started taking over 9 minutes during post-job cleanup, whereas it previously completed in just a few seconds.
Logs show the following timeout error:
Warning: Failed to restore: getCacheEntry failed: connect ETIMEDOUT 52.152.245.137:443
This appears to be a known issue with the caching action being used. A fix has been proposed via a pull request in the action’s repository, but it has not been merged by the maintainer, despite being open for several weeks.
Issue: https://github.com/ScribeMD/docker-cache/issues/837
Sample Action Link: https://github.com/openedx/edx-platform/actions/runs/15348929037/job/43191991538
Should we migrate the fork recommended in the fix PR?
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 with the unit-tests workflow's "Cache Docker Images" step and the linked sample run to confirm where post-job cleanup stalls. Read ScribeMD/docker-cache issue 837 and its proposed fix, then determine whether the recommended fork can replace the current action. Done means the workflow completes cleanup without the timeout or multi-minute delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100