cache: too slow cleanup
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
I'm opening this issue as a blank issue because it's still not clear if this is a bug!
For some reason, calling the cache save function in the post phase seems to cause a lot of blank time after uploading the cache. This did not happen until a few months ago, if I remember correctly. I just want to check if the actions team has a clear idea of what caused 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 delay when the cache save function runs in the post phase, comparing behavior after the cache upload with earlier behavior if possible. The issue is done when the cause of the blank time is identified and the appropriate change or follow-up is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100