CI: Process stale issues twice per day #116636
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This action starts with the first issue, then moves on to the next. Once it's processed a batch, it saves its progress in a small cache file.
As detailed in #113858, the rest of the CI generates lots of large cache files, which means the (small) actions/stale cache file has been cleared out by the time the next daily cron triggers.
This means the action starts again at the top, and reprocesses the same batch over and over, never making progress.
Let's try running twice a day. This should hopefully keep the "last access" of the cache file fresher, meaning it's not cleared out. We could later also try 3 or 4 times per day.