Swatantra-66 commented on issue #20483: URL: https://github.com/apache/nuttx/issues/20483#issuecomment-6139108789
Hi @acassis, To answer your question directly: 1. **No build failures or billing penalties:** There is no operational failure or extra cost. When cache storage reaches the 10 GB quota, GitHub Actions automatically applies a Least Recently Used (LRU) eviction policy, silently dropping the oldest unused cache entries to make space for new ones. 2. **The only minor drawback is cache churn:** High PR frequency means newer cache files can evict older caches from less frequently run matrix jobs, resulting in occasional cold builds for those specific targets. However, active targets will consistently hit warm caches and reduce compilation time. I completely agree with your suggestion to keep it running as-is for a few days to observe real-world CI compilation times and telemetry. If we notice too much churn later, we can always refine it so only `master` merges save new caches. In the meantime, we can monitor the runner metrics while moving forward with Phase 2! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
