Closed chronoxor closed 2 years ago
Looks like the issue in actions/cache - https://github.com/actions/cache/issues/698
I hit it once too getCacheEntry failed: connect ETIMEDOUT 13.107.42.16:443
Maybe we should be more forgiving in that case?
I think it might have been some temporary reliability issue on GitHub's side. @chronoxor is it still happening?
Maybe we should be more forgiving in that case?
Is there an explicit way of filtering that error apart from string matching?
Maybe we should be more forgiving in that case?
Is there an explicit way of filtering that error apart from string matching?
Not sure. Since even official actions failed and this was a real problem on GH's end maybe we shouldn't after all.
The issue was fixed on actions/cache side! The issue can be closed. But I think it's good idea to continue somehow even if cache is not available.
I have constantly returned cache service respond with error 500 for one of my projects:
Other projects with same github actions work fine!